tursodatabase / tursodatabase/libsql
Add metrics about rows returned
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
One user points out in our discord that having a metric about rows returned - and in particular, the ratio of rows returned by rows read, is a great way to assess the efficiency of indexes
thread for reference: https://discord.com/channels/933071162680958986/1233934841930580029/1233934841930580029
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
The issue names no files, tests, or entry points. Start by reading the referenced Discord thread to clarify which execution metrics are expected and how the rows-returned ratio should be defined. Done means exposing a rows-returned metric and the requested ratio in the appropriate metrics output, with coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100