influxdata / influxdata/influxdb
Programmatically matching queries with user data
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Proposal:
The proposal is for a means to provide make a query that defines requirements of data to call it. This is useful for pkger, in providing a contract that users can marry up their data too. It is also useful for any query to define what is required to use it.
Current behavior:
Does not exist. All flux queries are hand jammed to match users data. Very little reusability.
Desired behavior:
I want something that can just work automagically. I have a query that I use to grab some anomaly, I want to share this with other users so they can take advantage of it with their data as well.
Alternatives considered:
Continue hand jamming flux
Use case:
First use case is empowering resuable queries for pkger, but it can extend to any query user.
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 Flux queries and pkger as the initial use case but provides no files, tests, or entry points. Start by locating the existing query and user-data handling areas, then clarify the required contract, scope, and acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100