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 request: ability to delete/erase domain data added to RAG workspace #149

Open
saragerion opened this issue Oct 26, 2023 · 7 comments

Comments

@saragerion
Copy link

Summary

It could be useful to be able to selectively delete specific domain data added in the RAG workspace.
Domain data I am referring to includes:

  • Files uploaded
  • Text
  • Q/A
  • Websites

Motivation

There are some use cases in which a company may want or need to delete specific domain data after it has been added to the RAG storage. This can happen for example when companies need to adhere to compliance requirements and therefore should be able to erase private data from their workloads when requested.
Example: European Union’s General Data Protection Regulation (GDPR) “right to erasure” or “right to be forgotten” requirements, when applicable.

@ajaylamba-provar
Copy link
Contributor

Or the more common use case would be - the content has been updated.

@azaylamba
Copy link
Contributor

@flamingquaks @massi-ang I'm trying to make changes for this, could you guys give some pointers to start with please?

@azaylamba
Copy link
Contributor

azaylamba commented Jan 25, 2024

I am working on this one. I have successfully implemented this for OpenSearch but my fork is not in sync with main after migration to AppSync.
I will sync with main and will modify the code accordingly.

@azaylamba
Copy link
Contributor

Update: Changes are done, testing in progress.

Copy link

This issue is stale because it has been open for 60 days with no activity.

@azaylamba
Copy link
Contributor

Finally, raised PR for this.

@github-actions github-actions bot removed the stale label Apr 21, 2024
@azaylamba
Copy link
Contributor

azaylamba commented Jun 13, 2024

@saragerion Changes for this have been merged to main, this issue can be closed as done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants