[
https://issues.apache.org/jira/browse/PARQUET-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310704#comment-14310704
]
Mick Davies commented on PARQUET-36:
------------------------------------
I think functionally its the same, but for for queries I am running I would
like to push down IN predicates with a large number of entries, possibly a few
thousand.
I had imagined that using an IN operator based on a set would be faster,
certainly I think this would be important for the case when this predicate is
evaluated on a column that was not dictionary encoded.
Is there a reason why you think an IN (set) based operator could prove
problematic?
> FilteringPrimitiveConverter should support dictionaries
> -------------------------------------------------------
>
> Key: PARQUET-36
> URL: https://issues.apache.org/jira/browse/PARQUET-36
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Alex Levenson
> Priority: Minor
> Labels: filter2
>
> If the delegated PrimitiveConverter supports dictionaries, then
> FilteringPrimitiveConverter should too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
