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

Allow user to choose between five query types: simple, semantic, vector, simple-hybrid and simple-hybrid-vector from both /custom and /byod endpoints #897

Open
Tracked by #658
superhindupur opened this issue May 14, 2024 · 3 comments
Labels
subtask A subtask

Comments

@superhindupur
Copy link
Contributor

superhindupur commented May 14, 2024

Azure AI search allows five search query types:

  • simple | Represents the default, simple query parser.
  • semantic | Represents the semantic query parser for advanced semantic modeling.
  • vector | Represents vector search over computed data.
  • vector_simple_hybrid | Represents a combination of the simple query strategy with vector data.
  • vector_semantic_hybrid | Represents a combination of semantic search and vector data querying.

As of writing this, Chat with your data only supports vector_simple_hybrid and vector_semantic_hybrid. Under this issue, we want to allow the user to choose from any of the five query type options, so that they have full control over search query types from the configuration level.

@liammoat
Copy link
Collaborator

@superhindupur, can you clarify the "user" in this context? Should this be:

1 - A server-side configuration, that the user who deploys the service can set.
2 - A client-side configuration, that the user of the chat application can set.
3 - An admin-side configuration, that the user of the admin application can set.

@dhaksr
Copy link

dhaksr commented Jul 27, 2024

My vote would be for the client side configuration. allow the end user to experiment with search type would be good.

1 similar comment
@dhaksr
Copy link

dhaksr commented Jul 27, 2024

My vote would be for the client side configuration. allow the end user to experiment with search type would be good.

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

No branches or pull requests

4 participants