-
-
Notifications
You must be signed in to change notification settings - Fork 20.7k
Added meilisearch retriever component #2824
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
Conversation
…lity (FlowiseAI#3) meilisearch retriever component created , searching for an existing index and upserting a new or existing index has been implemented , component utilizes langchain and meilisearch vector search Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/3 Reviewed-by: mohamed1999akram <[email protected]>
…lowiseAI#4) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/4 Reviewed-by: mohammad <[email protected]>
… actions (FlowiseAI#5) added --no-lock-file flag to pass CICD , made the runner run on debian and not ubuntu , removed code that caused warnings to pass linting Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/5 Reviewed-by: omaryassery <[email protected]>
Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/6 Reviewed-by: omaryassery <[email protected]>
Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/7 Reviewed-by: isameh <[email protected]>
dockerfile-ntg modified to copy all working directory before calling pnpm install Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/9 Reviewed-by: isameh <[email protected]>
packages/components/nodes/retrievers/MeilisearchRetriever/MeilisearchRetriever.ts
Outdated
Show resolved
Hide resolved
packages/components/nodes/retrievers/MeilisearchRetriever/MeilisearchRetriever.ts
Outdated
Show resolved
Hide resolved
packages/components/nodes/retrievers/MeilisearchRetriever/MeilisearchRetriever.ts
Outdated
Show resolved
Hide resolved
@MohamedYasserOaf I've updated the code, and moved it into Vector Store folder, can you give this a test? |
I pulled the branch and applied pnpm install , the code fails on the build process , can't exactly point out the issue , i can send you the logs |
because this pulls in the main branch with 2.0 changes, you need to |
@HenryHengZJ I removed all the node_modules and followed your instructions , the issue still persist , maybe because my main is not up to date ? |
@HenryHengZJ my friend was able to run it too, I will check the dependencies from my side, you will find the documents upserted on your index but you will not get notified, this is a functionality i need to implement, maybe i can add it to this PR, you can try to chat with the flow to test in the meantime |
no I dont see anything upserted on Meilisearch, and chatting with it always return nothing |
I will lookup the issue after solving my build issue, we are already using our custom flowise image with meilisearch retriever in our production environment, providing great results, will check and come back to you |
@HenryHengZJ Hello Henry, I resolved my dependency problems and re-installed everything, I rebased with the latest commits from the main repository, now the build step fails because of a component called Melvis, the same happens with my friend
the above line causes the problem ![]() The code build when I apply @ts-ignore on this line ![]()
|
yeah I realized thhat as well and solved this in this PR did you upsert the data on Flowise? or you are just using for retrieval? |
yes I upserted using the flow, you tried doing so ? we use a UI to visualize our indexes، I can shoot you a small video or a series of screenshots of the process, we also added features like an option to delete an index, we added metadata as searchable attributes for appling various filters when retrieving. |
ah okay because I was not able to do so when I try upserting, so I wonder did that work for you. feel free to send me the screenshot/videos! |
@HenryHengZJ Hello henry, the following screenshot shows the whole process, This is a screenshot of our flow, the index used is "my-index-1" , test bool document store contains around 7 pdfs chunked using unstructured.io These screenshots shows "my-index-1" having 0 documents The following screenshot shows my flowise upsert window this is my index after upserting This is a screenshot of my chat window using my flow, you can see it has retrieved context from my upserted index
|
Thanks for the screenshot! |
* added meilisearch retriever and credentials.ts * added semantic ratio * removed a TODO implementatio * meilisearch component implemented with searching and upsert functionality (FlowiseAI#3) meilisearch retriever component created , searching for an existing index and upserting a new or existing index has been implemented , component utilizes langchain and meilisearch vector search Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/3 Reviewed-by: mohamed1999akram <[email protected]> * added CI/CD for ntg branch, added proper dockerfile for flowise-ntg (FlowiseAI#4) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/4 Reviewed-by: mohammad <[email protected]> * modified os version , removed linting errors , removed cypress github actions (FlowiseAI#5) added --no-lock-file flag to pass CICD , made the runner run on debian and not ubuntu , removed code that caused warnings to pass linting Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/5 Reviewed-by: omaryassery <[email protected]> * removed unnecessary QEMU install action (FlowiseAI#6) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/6 Reviewed-by: omaryassery <[email protected]> * removed cypress installation and linting from dockerfile (FlowiseAI#7) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/7 Reviewed-by: isameh <[email protected]> * dockerfile-ntg-modification (FlowiseAI#9) dockerfile-ntg modified to copy all working directory before calling pnpm install Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/9 Reviewed-by: isameh <[email protected]> * resolved comments, reverted CI/CD * add test docker build yml back * moved meilisearch to vector store folder * Update Meilisearch.ts --------- Co-authored-by: Henry <[email protected]> Co-authored-by: Henry Heng <[email protected]>
* added meilisearch retriever and credentials.ts * added semantic ratio * removed a TODO implementatio * meilisearch component implemented with searching and upsert functionality (FlowiseAI#3) meilisearch retriever component created , searching for an existing index and upserting a new or existing index has been implemented , component utilizes langchain and meilisearch vector search Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/3 Reviewed-by: mohamed1999akram <[email protected]> * added CI/CD for ntg branch, added proper dockerfile for flowise-ntg (FlowiseAI#4) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/4 Reviewed-by: mohammad <[email protected]> * modified os version , removed linting errors , removed cypress github actions (FlowiseAI#5) added --no-lock-file flag to pass CICD , made the runner run on debian and not ubuntu , removed code that caused warnings to pass linting Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/5 Reviewed-by: omaryassery <[email protected]> * removed unnecessary QEMU install action (FlowiseAI#6) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/6 Reviewed-by: omaryassery <[email protected]> * removed cypress installation and linting from dockerfile (FlowiseAI#7) Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/7 Reviewed-by: isameh <[email protected]> * dockerfile-ntg-modification (FlowiseAI#9) dockerfile-ntg modified to copy all working directory before calling pnpm install Reviewed-on: https://git.beyond.cc/ntg/flowise/pulls/9 Reviewed-by: isameh <[email protected]> * resolved comments, reverted CI/CD * add test docker build yml back * moved meilisearch to vector store folder * Update Meilisearch.ts --------- Co-authored-by: Henry <[email protected]> Co-authored-by: Henry Heng <[email protected]>
for the past 2 weeks , we needed to implement a retriever that utilized meilisearch for hybrid search powered retrieval , the component was created as a custom retriever, you either search an existing index using meilisearch and retrieve context for your LLM or you can upsert an existing or a new index to include new files that can be read using any flowise powered document store or document reading function, then you can retrieve context from this new index, more modifications and improvements may be introduced in future PRs, some commits are related to our personal CI/CD pipeline which can be ignored or re-modified after merge, kindly have a look and address any issues in the comments