posit-dev / posit-dev/raghilda
Feature Request: Key-Only Storage Mode (Remote Text Retrieval)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 36
- Forks
- 0
- Avg merge
- 17m
- Merged PRs (30d)
- 3
Description
Storing raw document text in the local DuckDB file is a blocker for data-sensitive environments. Teams subject to data controls may not be able to store plaintext content locally, even privately.
A "reference key mode" that persists only a reference key alongside each index entry but never writes the raw text to disk would be useful here. At query time, the caller resolves keys to content via a provided callback or some other way.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the DuckDB index persistence and query entry points, then trace where raw document text is currently stored and retrieved. Define how reference keys are persisted and how the caller-provided resolver supplies content at query time; done means plaintext is never written locally while keyed queries still retrieve the intended content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100