-
Notifications
You must be signed in to change notification settings - Fork 61
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
Real-time ingest feature #466
Comments
hi eric, long time no talk 😄 currently, there is no support for that, though you could write some custom routes/endpoints that wrap the ingest logic in the relatedly, we're moving some of that logic to the |
FWIW, I now have the 'ingest' running as an endpoint on an Azure function app (serverless function). Next step is a wrapper code that can take the source of the modified content (in my case, an external CMS) and accordingly call the server-less endpoint. |
nice! just to clarify what you mean, did you created an endpoint that's like did you make separate somewhat related, i think it would be really neat to have embedding occur as an event-based process whenever a page is updated. would be pretty straightforward with MongoDB change streams. you'd just need to build some basic event queue to process the page creation/change/deletion events to take into account rate limit issues with the embedding models. |
yes POST /ingest that takes an array of strings in body's argument.
changed doAllCommand args to
and updated doAllCommand to call
doPagesCommand and doEmbedCommand already took 'source' as string[] |
nice. this is great feedback. i realistically don't think that we'll create an ingest API anytime soon since we don't have need on our end. however, i would like to cleanly expose the ingestion methods so you or others can do something like what you've done w/o having to do anything hacky. like a "MongoDB RAG Ingest SDK". |
Hi,
Is there a way to use the Ingest package to be more "real-time", API driven?
Use case:
We have an FAQ which is updated quite often in a CMS.
Goal would be to trigger an ingestion of the content on every Create/Update/Delete operation in the CMS.
Is it possible with some little effort?
The text was updated successfully, but these errors were encountered: