Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[0.10] can't run CQs with the same name but scoped to different databases #5814

Closed
beckettsean opened this issue Feb 23, 2016 · 2 comments
Closed

[0.10] can't run CQs with the same name but scoped to different databases #5814

beckettsean opened this issue Feb 23, 2016 · 2 comments
Assignees
@jsternberg
Labels
area/continuous queries
Milestone
0.11.0

Comments

@beckettsean
Copy link
Contributor

From mailing list: https://groups.google.com/d/msgid/influxdb/7b74ce6c-d841-43f5-aeca-39fb860cdeec%40googlegroups.com

If multiple CQs exist with the same name but on different databases, only one CQ is actually executed.
@jsternberg jsternberg self-assigned this Feb 24, 2016
@jsternberg
Copy link
Contributor

It looks like the map storing the last run doesn't include the database name, so the CQ name isn't scoped there.

Preparing a fix for this. Do we need to backport this and do a bugfix release for 0.10 or can this just go directly into master and wait for 0.11?

@jsternberg jsternberg mentioned this issue Feb 24, 2016
Merged
@jsternberg jsternberg added this to the 0.11.0 milestone Feb 24, 2016
@jsternberg jsternberg mentioned this issue Feb 24, 2016
Closed
@rkuchan rkuchan mentioned this issue Feb 24, 2016
Closed
jsternberg added a commit that referenced this issue Feb 24, 2016
@jsternberg
Fix running multiple CQs with the same name
0730573 
Previously, CQs with the same name would be stored in the last run map
the same way. This caused only one of the CQs to run because after the
first one ran it would update the last run time for all CQs with the
same name.

Add the database name to the CQ ID in the last run map to differentiate
between CQs in different databases.

Fixes #5814.
@beckettsean
Copy link
Contributor Author

@jsternberg this is a pretty minor issue with a simple workaround, so I see no need to backport to 0.10. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jsternberg jsternberg

Labels
area/continuous queries
Projects
None yet
Milestone
0.11.0
Development

No branches or pull requests
2 participants
@jsternberg @beckettsean