influxdata / influxdata/kapacitor
Be able to convert a batch to a stream explicitly
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
While most nodes can handle batch or stream data there are a few cases where an explicit conversion is appropriate.
1. For a UDF that can only handle a single edge type.
2. For streaming aggregate functions, i.e. movingAverage and cumulativeSum both reset counters on batch boundaries. A user may wish to remove those boundaries explicitly.
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by locating Kapacitor's batch and stream data-handling paths and determine where an explicit conversion could be exposed; done means both listed use cases can request conversion and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100