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.

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

query: multiple 'query.replica-label' flag #1571

Closed
amalucelli opened this issue Sep 26, 2019 · 4 comments · Fixed by #1578
Closed

query: multiple 'query.replica-label' flag #1571

amalucelli opened this issue Sep 26, 2019 · 4 comments · Fixed by #1578

Comments

@amalucelli
Copy link

Thanos, Prometheus and Golang version used:

thanos, version 0.7.0 (branch: HEAD, revision: c6eaf68bec32aefd280318eaef6121d6ddb20d10)
  build user:       circleci@f199bdee6152
  build date:       20190902-15:43:19
  go version:       go1.12.5

What happened

I got this error message when I tried to use multiple flags on the query component:

flag 'query.replica-label' cannot be repeated

What you expected to happen

As implemented on this PR (#1362), I was expecting to be able to use multiple flags :) maybe I'm missing something.

I even saw on the CHANGELOG this topic described:

#1362 query.replica-label configuration can be provided more than once for multiple deduplication labels like: --query.replica-label=prometheus_replica --query.replica-label=service.

I also followed the latest documentation that instruct on how to use it.

How to reproduce it (as minimally and precisely as possible):

docker run --rm thanosio/thanos:v0.7.0 query --query.replica-label=prometheus_replica --query.replica-label=prometheus_region

Error parsing commandline arguments: flag 'query.replica-label' cannot be repeated
usage: thanos query [<flags>]
@brancz
Copy link
Member

brancz commented Sep 26, 2019

cc @krasi-georgiev

@yeya24
Copy link
Contributor

yeya24 commented Sep 26, 2019

Are you using release v0.7.0? #1362 is not included in it. If you want to use this feature, you can build from master. This works for me

@amalucelli
Copy link
Author

@yeya24 yeah, maybe I got confused, idk.. I saw this change on the CHANGELOG under v0.7.0, that's why

@jojohappy
Copy link
Member

Hi, maybe it is our fault. #1362 is merged after v0.7.0 released.

Will fix CHANGELOG soon. Sorry for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants