influxdata / influxdata/iot-api-js
Stream query results
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 5
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 2
Description
> `query()` buffers the entire result set into memory before returning. For large measurement queries, this can cause high memory usage and slow responses (the previous implementation streamed lines). Consider adding a streaming option (async iterator passthrough) or enforcing limits/pagination at the API boundary.
_Originally posted by @Copilot in [#18](https://github.com/influxdata/iot-api-js/pull/18/changes/BASE..b878619913d2aeb51d50a514c004bebbf4c9873b#r2785044209)_
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
Begin at the query() entry point and review the previous streaming implementation referenced in PR #18. Reproduce a large measurement query to observe the current buffering behavior. Done means implementing and verifying an agreed approach for streaming results or enforcing API-boundary limits or pagination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100