Skip to content
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

Feature/Return SourceDocuments #274

Merged
merged 1 commit into from
Jun 9, 2023

Conversation

HenryHengZJ
Copy link
Contributor

Add ability to return source documents when using ConversationalRetrievalQAChain:

returnSrcDocs.mp4

@trepont
Copy link

trepont commented Jul 3, 2023

I've been able to

convert my docs into embeddings and stored into pinecone index/namespace
use that index/namespace embedding in pinecone to power a conversational agent
and SEPERATELY, create a number of conversational agents which use collected web browser (directed) or Serp (search) web results to chain them and use ChatGPT for inference
bu i am facing issue with retun SourceDocuments in this scenario,how to use return SourceDocuments for multple chains scenario
is that possible either now or in the future?
Thanks in advance.

@segelmache
Copy link

Hi there, it would be very helpful, if the returned sources would be limited to the sources, the model actually used for its answer. Would that be possible? Otherwise, if it's getting 50 documents from the vector database, all sources of thouse 50 documents would be displayed.

JohnBQuinn pushed a commit to JohnBQuinn/Flowise that referenced this pull request Jun 7, 2024
* feat: retry send

* perf: qa default value

* feat: dataset folder

* feat: kb folder delete and path

* fix: ts

* perf: script load

* feat: fileCard and dataCard

* feat: search file

* feat: max token

* feat: select dataset

* fix: preview chunk

* perf: source update

* export data limit file_id

* docs

* fix: export limit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants