-
Notifications
You must be signed in to change notification settings - Fork 9
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
database collection crud endpoints #16
Comments
That's a good one - I would have done the same, custom component wrapped in a pipeline that's just there for the purpose of invoking that component. But the line between a clever use of hayooks' design and a hack is blurry here, I wonder if we should support explicitly the customization of the internal FastAPI router... |
the component turned out to be quite simple:
alternatively, I could commit it to qdrant integrations for re-usage |
That's great @Rusteam! Please tag me if you contribute the component to the integration, I can review! |
We're using
hayhooks
to servehaystack
pipelines and we need a way to find out which collections are already present in the vector db (qdrant). We've decided to build a custom component and deploy it, however I wonder if it's better to create these methods for fastapi by default?The text was updated successfully, but these errors were encountered: