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

Accessing EvaDB tables using Postgres query engine #1331

Open
1 of 2 tasks
pchunduri6 opened this issue Nov 1, 2023 · 1 comment
Open
1 of 2 tasks

Accessing EvaDB tables using Postgres query engine #1331

pchunduri6 opened this issue Nov 1, 2023 · 1 comment
Labels
Data Sources Features/Bugs related to Data Sources Documentation 📗 User Experience

Comments

@pchunduri6
Copy link
Contributor

Search before asking

  • I have searched the EvaDB issues and found no similar feature requests.

Description

Currently, it is not clear whether we can access EvaDB tables using a different query engine like Postgres. This will be useful when we want to leverage Postgres features like window functions and string_agg on the output of EvaDB tables. One concrete workflow that benefits from this is RAG-based question-answering:

  1. Create vector index of a document in EvaDB.
  2. Use similarity to retrieve top-5 similar chunks to the user question.
  3. Concatenate all the retrieved chunks in Postgres using group by and string_agg.
  4. Run an LLM function on the concatenated output.

If this is not possible, we would need to add support for STRING_AGG and GROUP BY 'chunks' natively in EvaDB.

Use case

No response

Are you willing to submit a PR?

  • Yes I'd like to help by submitting a PR!
@pchunduri6 pchunduri6 added Documentation 📗 User Experience Data Sources Features/Bugs related to Data Sources labels Nov 1, 2023
@ryanmle2001
Copy link

Claimed for EvaDB Project 2 @jarulraj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Sources Features/Bugs related to Data Sources Documentation 📗 User Experience
Projects
None yet
Development

No branches or pull requests

2 participants