This repository was archived by the owner on Aug 23, 2023. It is now read-only.
Conversation
robert-milan
approved these changes
Jan 29, 2020
Contributor
is this reverting a specific PR or commit? which one? do we know the performance ramifications? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is just undoing what was supposed to be a performance optimization.
Fixes: #1648
Tested with this scenario:
Created two metrics with
fakemetrics:some.id.of.a.metric.1;anothertag=somelongervaluesome.id.of.a.metric.2Created meta record:
Using
master, I call theautoCompleteendpoint and get a result for the metric ending in.1(metric tag) but not for the one ending with.2(meta tag):Using this branch, I do the same two calls one more time, and now i get a result for both of them:
They can also be mixed in a single call: