[
https://issues.apache.org/jira/browse/DRILL-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746640#comment-14746640
]
Aman Sinha commented on DRILL-3788:
-----------------------------------
[~rkins] can you try to create a smaller repro ? Given the nature of the issue
it shouldn't require large number of files.
[~sphillips] does the metadata cache store the min/max values for a column in a
row group to determine if it is single_value ? Any thoughts on what is missing
to get partition pruning to work with metadata caching ?
> Partition Pruning not taking place with metadata caching when we have ~20k
> files
> --------------------------------------------------------------------------------
>
> Key: DRILL-3788
> URL: https://issues.apache.org/jira/browse/DRILL-3788
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 1.2.0
> Reporter: Rahul Challapalli
> Assignee: Aman Sinha
> Priority: Critical
> Fix For: 1.2.0
>
> Attachments: plan.txt
>
>
> git.commit.id.abbrev=240a455
> Partition Pruning did not take place for the below query after I executed the
> "refresh table metadata command"
> {code}
> explain plan for
> select
> l_returnflag,
> l_linestatus
> from
> `lineitem/2006/1`
> where
> dir0=1 or dir0=2
> {code}
> The logs did not indicate that "pruning did not take place"
> Before executing the refresh table metadata command, partition pruning did
> take effect
> I am not attaching the data set as it is larger than 10MB. Reach out to me if
> you need more information
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
