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

Model search API has different behavior depending on if system index is created or not #1425

Open
jmazanec15 opened this issue Jan 26, 2024 · 0 comments
Labels
Enhancements Increases software capabilities beyond original client specifications

Comments

@jmazanec15
Copy link
Member

Description

Currently, when running the model search api, if the model index does not exist, it will throw an exception. If it does exist, it will return empty hits. The problem with this is that it leaks implementation details about the model system to the user. A user in general should not need to know about the backing system index in order to use the functionality.

Expected Behavior

If there are no models matching a query, return a consistent result, regardless of whether the backing index is created or not.

@jmazanec15 jmazanec15 added Enhancements Increases software capabilities beyond original client specifications and removed untriaged labels Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancements Increases software capabilities beyond original client specifications
Projects
None yet
Development

No branches or pull requests

1 participant