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

on high cardinality dim filters and metric sorting use case can not be multiengine query, has to be single engine query #390

Open
pranavbhole opened this issue Jan 14, 2019 · 0 comments

Comments

@pranavbhole
Copy link
Contributor

When there is dim filtering on campaign name field and metric sorting, then multiengine use case prefers metrics sorting over dim filtering and query returns inconsistent results.

Fix: Ideally for dim filters other then status,id (high cardinality filters), and metrics sorting use case should go to oracle only. This case can not be multiengine use case.

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

No branches or pull requests

2 participants
@pranavbhole and others