influxdata / influxdata/kapacitor

Window node does not populate data prior to task definition

Open
#1,948 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

The tick script expects window of the last 4h values to be emitted every 1m for further processing.
However just after task definition the emitted data is empty, and then it gets populated with more values, starting from 1m range.

Expected behavior is that 4h window is emitted right from the start of the task.

```
stream
|from()
.measurement('cpu')
|window()
.period(4h)
.every(1m)
|httpOut('4h')
```

```
kapacitor stats general
ClusterID: 14aecaee-b88b-420b-9eaa-4e572a0035f6
ServerID: 30a9d71d-e00a-4833-b3bb-e6dd88016b93
Host: localhost
Tasks: 1
Enabled Tasks: 1
Subscriptions: 6
Platform: OSS
Version: v1.5.0
```

```
influx -version
InfluxDB shell version: v1.5.3
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the provided tick script with the 4h window and 1m emission settings against the reported Kapacitor and InfluxDB versions. Inspect the window node's behavior immediately after task definition; done means the first emitted window contains the prior 4h of values rather than starting empty and growing from 1m.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
stream-processing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.