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

store: support for <> != <val> matcher is not implemented after upgrade to V0.3.0 #834

Closed
arnitolog opened this issue Feb 11, 2019 · 2 comments
Labels

Comments

@arnitolog
Copy link
Contributor

Thanos, Prometheus and Golang version used

  • Thanos: all components 0.3.0
  • Prometheus: 2.7.1

What happened
After upgrading query and store components from 0.2.1 to 0.3.0 we started seeing below errors for queries which use "not-equal" (!=) binary operator:

receive series: rpc error: code = Aborted desc = fetch series for block 01D3EFDYWZ6WX3C1SEHF3ESA95: expanded matching posting: match labels: support for <> != <val> matcher is not implemented; empty matcher for label name mode

What you expected to happen
query component returns the correct value

How to reproduce it (as minimally and precisely as possible):
any query with != (not-equal) binary operator. My, in particular, looks like:
node_cpu_seconds_total{mode!="idle"}
Full logs to relevant components

Anything else we need to know

@arnitolog arnitolog changed the title query: support for <> != <val> matcher is not implemented after upgrade to V0.3.0 query/store: support for <> != <val> matcher is not implemented after upgrade to V0.3.0 Feb 11, 2019
@bwplotka bwplotka changed the title query/store: support for <> != <val> matcher is not implemented after upgrade to V0.3.0 store: support for <> != <val> matcher is not implemented after upgrade to V0.3.0 Feb 12, 2019
@bwplotka bwplotka added the bug label Feb 12, 2019
@bwplotka
Copy link
Member

Fix in progress.

@bwplotka
Copy link
Member

#839

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

No branches or pull requests

2 participants