quickwit-oss / quickwit-oss/quickwit
Add GIN index on `splits.tags` (PostgreSQL metastore)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
currently we create no index on any postgres columns, but some indexes could be useful.
I think split is the table with the most potential for indexes: it's often the biggest.
it's index_uid column is used in every query, there is probably some substantial gain from having a simple hash index on that:
CREATE INDEX index_splits_index_uid ON splits USING HASH (index_uid);
other column should probably be looked at too, but would likely have a less sever impact
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
No file or test is named. First locate the PostgreSQL metastore schema and index-creation path, then reconcile the title’s request for a GIN index on splits.tags with the body’s example of a hash index on index_uid. Done means the intended column and index type are confirmed and the PostgreSQL index is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100