influxdata / influxdata/kapacitor

Task may subscribe to the same dbrp more than once (Bug?)

Open
#1,504 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Master at 055e09f

```
kapacitor define o -tick example.tick -dbrp telegraf.autogen -dbrp telegraf.autogen -type stream
~/kap/etc$ kapacitor show o
ID: o
Error:
Template:
Type: stream
Status: disabled
Executing: false
Created: 31 Jul 17 11:15 EDT
Modified: 31 Jul 17 11:15 EDT
LastEnabled: 01 Jan 01 00:00 UTC
Databases Retention Policies: ["telegraf"."autogen" "telegraf"."autogen"]
TICKscript:
var x = 10

var data = stream
|from()
.measurement('cpu')
|alert()
.crit(lambda: TRUE)
.message('hello' + string(x))

DOT:
digraph o {
stream0 -> from1;
from1 -> alert2;
}
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the duplicate -dbrp command shown in the issue and tracing how task database-retention-policy subscriptions are handled. The issue does not state whether duplicates should be rejected or deduplicated, so confirm the intended behavior before changing code; done should include coverage for repeated DBRP arguments.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases
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.