Mintplex-Labs/vector-admin
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/vector-admin.git synced 2026-07-15 19:27:30 -04:00
Code Issues 79 Packages Projects Releases Wiki Activity

[BUG]: Weaviate: Indexes seem to be queries with underscores removed? #76

New Issue
Open
opened 2026-02-15 16:30:03 -05:00 by yindo · 10 comments
yindo commented 2026-02-15 16:30:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @bbrala on GitHub (Jul 6, 2024).

How are you running VectorAdmin?

Docker (local)

What happened?

Error when trying to sync.

Are there known steps to reproduce?

Connected to weaviate with existing named classes that do not use camelcase, then you get following messages consistently when trying to sync.

vector-admin | ClientError: Cannot query field "Bp10153C51068DocumentChunksV1" on type "GetObjectsObj". Did you mean "Bp101_53c51068_documentChunks__v1", "Bp131_13b35c33_documentChunks", "Bp160_15dede47_documentChunks", "Bp100_e19743d9_documentChunks__v1", or "Bp48_8ae7d6f8_documentChunks__v1"?: {"response":{"errors":[{"locations":[{"column":6,"line":1}],"message":"Cannot query field \"Bp10153C51068DocumentChunksV1\" on type \"GetObjectsObj\". Did you mean \"Bp101_53c51068_documentChunks__v1\", \"Bp131_13b35c33_documentChunks\", \"Bp160_15dede47_documentChunks\", \"Bp100_e19743d9_documentChunks__v1\", or \"Bp48_8ae7d6f8_documentChunks__v1\"?","path":null}],"status":200,"headers":{}},"request":{"query":"{Get{Bp10153C51068DocumentChunksV1(limit:1){_additional { vector }}}}"}}

And

vector-admin | Weaviate:namespaceCountWithClient Cannot query field "Bp111F0880665DocumentChunksV1" on type "AggregateObjectsObj". Did you mean "Bp126_0dcea379_documentChunks", "Bp138_15a0c090_documentChunks__v1", "Bp58_ee2680db_documentChunks__v1", "Bp111_f0880665_documentChunks__v1", or "Bp125_414b683f_documentChunks"?: {"response":{"errors":[{"locations":[{"column":12,"line":1}],"message":"Cannot query field \"Bp111F0880665DocumentChunksV1\" on type \"AggregateObjectsObj\". Did you mean \"Bp126_0dcea379_documentChunks\", \"Bp138_15a0c090_documentChunks__v1\", \"Bp58_ee2680db_documentChunks__v1\", \"Bp111_f0880665_documentChunks__v1\", or \"Bp125_414b683f_documentChunks\"?","path":null}],"status":200,"headers":{}},"request":{"query":"{Aggregate{Bp111F0880665DocumentChunksV1{meta { count }}}}"}}

And more of those.

Originally created by @bbrala on GitHub (Jul 6, 2024). ### How are you running VectorAdmin? Docker (local) ### What happened? Error when trying to sync. ### Are there known steps to reproduce? Connected to weaviate with existing named classes that do not use camelcase, then you get following messages consistently when trying to sync. > ``` vector-admin | ClientError: Cannot query field "Bp10153C51068DocumentChunksV1" on type "GetObjectsObj". Did you mean "Bp101_53c51068_documentChunks__v1", "Bp131_13b35c33_documentChunks", "Bp160_15dede47_documentChunks", "Bp100_e19743d9_documentChunks__v1", or "Bp48_8ae7d6f8_documentChunks__v1"?: {"response":{"errors":[{"locations":[{"column":6,"line":1}],"message":"Cannot query field \"Bp10153C51068DocumentChunksV1\" on type \"GetObjectsObj\". Did you mean \"Bp101_53c51068_documentChunks__v1\", \"Bp131_13b35c33_documentChunks\", \"Bp160_15dede47_documentChunks\", \"Bp100_e19743d9_documentChunks__v1\", or \"Bp48_8ae7d6f8_documentChunks__v1\"?","path":null}],"status":200,"headers":{}},"request":{"query":"{Get{Bp10153C51068DocumentChunksV1(limit:1){_additional { vector }}}}"}} ``` And > ``` vector-admin | Weaviate:namespaceCountWithClient Cannot query field "Bp111F0880665DocumentChunksV1" on type "AggregateObjectsObj". Did you mean "Bp126_0dcea379_documentChunks", "Bp138_15a0c090_documentChunks__v1", "Bp58_ee2680db_documentChunks__v1", "Bp111_f0880665_documentChunks__v1", or "Bp125_414b683f_documentChunks"?: {"response":{"errors":[{"locations":[{"column":12,"line":1}],"message":"Cannot query field \"Bp111F0880665DocumentChunksV1\" on type \"AggregateObjectsObj\". Did you mean \"Bp126_0dcea379_documentChunks\", \"Bp138_15a0c090_documentChunks__v1\", \"Bp58_ee2680db_documentChunks__v1\", \"Bp111_f0880665_documentChunks__v1\", or \"Bp125_414b683f_documentChunks\"?","path":null}],"status":200,"headers":{}},"request":{"query":"{Aggregate{Bp111F0880665DocumentChunksV1{meta { count }}}}"}} ``` And more of those.
yindo added the bugcore-team labels 2026-02-15 16:30:03 -05:00
yindo commented 2026-02-15 16:30:04 -05:00
Author
Owner
Copy Link
Copy Source

@bbrala commented on GitHub (Jul 6, 2024):

After changing all this.camelCase things to seem to sync.

Very ugly hack:
embeddings-fix.patch

@bbrala commented on GitHub (Jul 6, 2024): After changing all this.camelCase things to seem to sync. Very ugly hack: [embeddings-fix.patch](https://github.com/user-attachments/files/16117394/embeddings-fix.patch)
yindo commented 2026-02-15 16:30:04 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 7, 2024):

Was this namespace created by AnythingLLM or was it already existing? We shouldn't have issues with referring to spaces created via AnythingLLM since in theory, the rules of namespace should be consistent from creation/update/read/delete

@timothycarambat commented on GitHub (Jul 7, 2024): Was this namespace created by AnythingLLM or was it already existing? We shouldn't have issues with referring to spaces created via AnythingLLM since in theory, the rules of namespace should be consistent from creation/update/read/delete
yindo commented 2026-02-15 16:30:04 -05:00
Author
Owner
Copy Link
Copy Source

@bbrala commented on GitHub (Jul 8, 2024):

No it was an existing one. Was under the inpression it would allow some interfacing to our existing weaviate database.

@bbrala commented on GitHub (Jul 8, 2024): No it was an existing one. Was under the inpression it would allow some interfacing to our existing weaviate database.
yindo commented 2026-02-15 16:30:04 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 8, 2024):

Ah, so technically speaking, if the workspace and the namespace in Weaviate have the same slug value - it would work when it returns vector search results, but they would never show in citations and the embeddings created out of AnythingLLM need to have a text metadata property to even be injected. This kind of use-case is not explicitly supported because of the litany of possible issues from someone embedding their data in any way they deem fit and it not being compatible with the way AnythingLLM expects and manages vectors and their associated metadata.

@timothycarambat commented on GitHub (Jul 8, 2024): Ah, so technically speaking, if the workspace and the namespace in Weaviate have the same `slug` value - it _would_ work when it returns vector search results, but they would never show in citations **and** the embeddings created out of AnythingLLM need to have a `text` metadata property to even be injected. This kind of use-case is not explicitly supported because of the litany of possible issues from someone embedding their data in any way they deem fit and it not being compatible with the way AnythingLLM expects and manages vectors and their associated metadata.
yindo commented 2026-02-15 16:30:04 -05:00
Author
Owner
Copy Link
Copy Source

@bbrala commented on GitHub (Jul 9, 2024):

Ok so vector admin is technically AnythingLVM-admin?

Unfortunate. Thanks.

@bbrala commented on GitHub (Jul 9, 2024): Ok so vector admin is technically AnythingLVM-admin? Unfortunate. Thanks.
yindo commented 2026-02-15 16:30:05 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 9, 2024):

No, they are two totally separate repos. If it was just for anythingLLM it would be in this repo

@timothycarambat commented on GitHub (Jul 9, 2024): No, they are two totally separate repos. If it was just for anythingLLM it would be in this repo
yindo commented 2026-02-15 16:30:05 -05:00
Author
Owner
Copy Link
Copy Source

@bbrala commented on GitHub (Jul 10, 2024):

Ok, but you do not aim to support existing databases then. Having fixed rules on how things are named seems kinda counter intuitive.

I could contribute a setting of some sort to enable/disable the forces camelcase if you like.

@bbrala commented on GitHub (Jul 10, 2024): Ok, but you do not aim to support existing databases then. Having fixed rules on how things are named seems kinda counter intuitive. I could contribute a setting of some sort to enable/disable the forces camelcase if you like.
yindo commented 2026-02-15 16:30:05 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 10, 2024):

I just realized we have been talking on the vector-admin repo which explains all the confusion. This whole time I thought this was AnythingLLM's repo where I get 99% of issues/notifications.

This is a bug for VA, lol. Yes underscores should not matter in this context

@timothycarambat commented on GitHub (Jul 10, 2024): I just realized we have been talking on the `vector-admin` repo which explains all the confusion. This whole time I thought this was AnythingLLM's repo where I get 99% of issues/notifications. This is a bug for VA, lol. Yes underscores should not matter in this context
yindo commented 2026-02-15 16:30:06 -05:00
Author
Owner
Copy Link
Copy Source

@bbrala commented on GitHub (Jul 10, 2024):

Hehe, thanks :)

@bbrala commented on GitHub (Jul 10, 2024): Hehe, thanks :)
yindo commented 2026-02-15 16:30:06 -05:00
Author
Owner
Copy Link
Copy Source

@HassanAITBRIK commented on GitHub (Aug 19, 2024):

Any update about this issue ?

@HassanAITBRIK commented on GitHub (Aug 19, 2024): Any update about this issue ?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Docker
UI/UX
UI/UX
bug
bug
core-team
core-team
core-team
documentation
enhancement
enhancement
feature request
good first issue
invalid
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label bug core-team
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/vector-admin#76
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?