stackql / stackql/stackql-devel
[FEATURE] Query cost optimiser
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Feature Description
A clear and concise description of what you want to happen.
Example(s)
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Possible Approaches or Libraries to Consider
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
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, entry points, concrete behavior, or acceptance criteria. Start by surveying the repository for query planning and execution entry points, then clarify the optimizer's scope, inputs, and expected cost-based decisions with maintainers. Done requires an agreed design and tests covering the defined behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100