tursodatabase / tursodatabase/libsql
Add a way to specify `timeout` in HRANA protocol
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Right now, there is no way to specify a timeout in the query; it is decided by the server. The server usually kills the query if it is taking "too long". However, there are certain classes of queries that we know for sure will take time, like for example, index creation. In such situations, we want the query to specify the timeout and override the server's default setting.
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 reading the HRANA protocol handling for queries and tracing where the server applies its default timeout. Determine how a query-specified timeout should be represented and propagated. Done means eligible queries can provide a timeout that overrides the server default, while existing behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100