-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat(api): MultiQueryRetriever with WeaviateHybridSearchRetriever #153
Conversation
Deploying with Cloudflare Pages
|
@Lee-W Now that we have We should try the following:
Let me know if you need any you need to connect on this, please |
3eba162
to
a2f5ffe
Compare
|
||
from ask_astro.clients.weaviate_ import docsearch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
d25c8f6
to
3430a16
Compare
3430a16
to
80be59f
Compare
tested with 6. a bit better but might have room to improve
not yet have time to work on it today. will continue work on it early tomorrow |
a0e9816
to
0f0f8d0
Compare
close this one, as changes included in #170 |
Contradict to our earlier discussion; I suspect what we want to replace
WeaviateHybridSearchRetriever
with isMultiQueryRetriever
instead ofConversationalRetrievalChain
. However, it seems to perform even worse than theMultiQueryRetriever
when it comes to what is astro python sdk?. astronomer-providers, airflow things seem to work. For testing, we can use the same set of env var and the exact same way to bring up the test env locally.