Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hybrid should skip properties with indexSearchable=False #4869

Closed
1 task done
dirkkul opened this issue May 7, 2024 · 2 comments
Closed
1 task done

Hybrid should skip properties with indexSearchable=False #4869

dirkkul opened this issue May 7, 2024 · 2 comments
Assignees
Labels

Comments

@dirkkul
Copy link
Contributor

dirkkul commented May 7, 2024

How to reproduce this bug?

  • have a property that is indexSearchable=False
  • do a hybrid search without giving properties - might only happen with aggregate
  • get error

weaviate.exceptions.WeaviateQueryError: Query call with protocol GQL Aggregate failed with message Error in GraphQL response: [
  {
    "locations": [
      {
        "column": 12,
        "line": 1
      }
    ],
    "message": "shard VHQYjfGOV5hV: sparse search: aggregate sparse search: bm25 objects: Searching by property 'product_id' requires inverted index. Is `indexSearchable` option of property 'prop' enabled? Set it to `true` or leave empty",
    "path": [
      "Aggregate",
      "Collection"
    ]
  }
], for the following query: {Aggregate{Collection(objectLimit: 12 hybrid:{query: "query", alpha: 0.7}){meta{count}}}}.

What is the expected behavior?

no error

What is the actual behavior?

error

Supporting information

No response

Server Version

1.25.0-rc0

Code of Conduct

@donomii
Copy link
Contributor

donomii commented May 9, 2024

Confirmed this is only happening in aggregate

@rthiiyer82
Copy link

rthiiyer82 commented May 17, 2024

I can confirm in 1.25.1 patch version that the above error isn't shown when performing aggregate hybrid search have property with indexSearchable=False

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants