-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
any milestone or timetable on SDK of ragflow ? #1605
Comments
### What problem does this PR solve? #1605 ### Type of change - [x] New Feature (non-breaking change which adds functionality)
+1. I tried to use the python sdk recently, but got troubles on a simple knowledge base retrieval test. |
The SDK API and HTTP API are both being updated. Except for the documentation-related APIs, others has been mostly completed. You can refer to the latest api document python_api and code for reference. |
Thanks for your reply. Can I ask when will the python sdk become stable. We are considering if we can integrate RAGFlow as a knowledge retrieval backend in our custom system recently. |
What do you mean by |
Recently, I did a few test about the After looking into the source code, I found either the installed sdk (which comse from the main branch) doesn't match the docker image (i.e. And the api name and parameters are still changing these days. For instance, the Thus, I am wondering whether it is a good time for us to integrate RAGFlow using the python sdk right now. If it is still under quick development. Maybe we should wait for a few weeks until it become a stable version. |
Got it. |
### What problem does this PR solve? infiniflow#1605 ### Type of change - [x] New Feature (non-breaking change which adds functionality)
Describe your problem
it seems the sdk/python package and codebase is updating here.
I am wondering does any overall milestone or time table on it ? then we can easily integration on our current project. not too much code base incursions happen , thanks.
The text was updated successfully, but these errors were encountered: