influxdata / influxdata/influxql
Limit doesnot work with Group by for Influx v2, influxQL
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 170
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
Hi I am trying to implement Pagination while performing group by tags with influx v2 and java client.
I am performing limit query with group by tag I see that the pagination/limit does not work, Is there a way to apply limit ?
SELECT count("InspectionStatus") AS "count-InspectionStatus",count("System ID") AS "count-System ID",count("Link ID") AS "count-Link ID",count("Chain system id") AS "count-Chain system id",count("Loop Number") AS "count-Loop Number",count("leftcamerastatus") AS "count-leftcamerastatus",count("rightcamerastatus") AS "count-rightcamerastatus",count("Right camera") AS "count-Right camera",count("Left Camera") AS "count-Left Camera" FROM "CC3B" WHERE time >= '2024-03-01T05:00:00.000Z' AND time <= '2024-03-01T21:12:06.334Z' GROUP BY subtype,time(1d) ORDER BY time DESC LIMIT 100;
Contributor guide
No contributing guide indexed for this repository
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 source file, test, or entry point is identified in the issue. Start by reproducing the supplied InfluxQL query with GROUP BY, ORDER BY, and LIMIT, then determine whether the behavior is parser-related or requires database execution semantics; done means a confirmed explanation or a narrowly scoped fix with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100