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

Predicate pushdown is not working when a single table query has multiple conditions on the same column #140

Open
parekuti opened this issue Feb 22, 2017 · 1 comment
Assignees

Comments

@parekuti
Copy link
Contributor

For example =>
select x, y from person where x='GG' and y='3489' and y='0943'

2017-02-10 10:04:30,043] INFO filodb.spark.FiloRelation$ - Incoming filters = List(EqualTo(x,GG), EqualTo(y,3489), EqualTo(y,0943))
[2017-02-10 10:04:30,043] INFO filodb.spark.FiloRelation$ - Pushing down partition column x, filters List(EqualTo(x,GG))
[2017-02-10 10:04:30,043] INFO filodb.spark.FiloRelation$ - Pushing down partition column y, filters List(EqualTo(y,3489), EqualTo(y,0943))
[2017-02-10 10:04:30,043] INFO filodb.spark.FiloRelation$ - Push down partition predicates: List(Set(GG))

@parekuti parekuti changed the title Predicate pushdown is not working when a single table query has filters on the same column Predicate pushdown is not working when a single table query has multiple conditions on the same column Feb 22, 2017
@velvia
Copy link
Member

velvia commented Feb 24, 2017

To be more precise, when the same column has multiple = relations. It's arguable whether this is valid SQL or not (as it really should be OR and not AND) but we could probably parse it.

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