quickwit-oss / quickwit-oss/quickwit
IPFS storage and search
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Is your feature request related to a problem? Please describe.
I would like to be able to run searches on indexes stored on IPFS.
Describe the solution you'd like
The Storage trait in its current state requires you to implement both read and write functions which is problematic for IPFS. The final IPFS url where the index will be available cannot be known in advance. Potential solution is creating a local index, uploading it to IPFS, then querying it from IPFS directly.
The Storage trait could be broken down into two, StorageRead and StorageWrite. That would allow supporting the IPFS search without creating the index directly on IPFS.
Additional context
- https://github.com/ferristseng/rust-ipfs-api
- we still cannot query byte ranges from rust but that is coming
- It might be possible to build indexes directly on IPFS by pointing to an IPNS hash
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 Storage trait and reviewing how its read and write requirements relate to the rust-ipfs-api, byte-range support, and IPNS notes in the issue. Define whether StorageRead and StorageWrite are sufficient for querying an index uploaded to IPFS, then verify that searches work without requiring the final write URL in advance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100