[
https://issues.apache.org/jira/browse/DRILL-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377088#comment-14377088
]
Adam Gilmore commented on DRILL-2517:
-------------------------------------
I tried this already, but I just get the "table not found" error. I notice
there is some code in FileSelection at the moment that handles * and ?
explicitly:
{code}
public static FileSelection create(DrillFileSystem fs, String parent, String
path) throws IOException {
if ( !(path.contains("*") || path.contains("?")) ) {
Path p = new Path(parent, removeLeadingSlash(path));
FileStatus status = fs.getFileStatus(p);
return new FileSelection(Collections.singletonList(status),
p.toUri().getPath());
{code}
I would have thought the globbing would have been passed through to the
underlying storage though.
> Partition pruning still reading files during planning
> -----------------------------------------------------
>
> Key: DRILL-2517
> URL: https://issues.apache.org/jira/browse/DRILL-2517
> Project: Apache Drill
> Issue Type: Bug
> Components: Query Planning & Optimization
> Affects Versions: 0.7.0, 0.8.0
> Reporter: Adam Gilmore
> Assignee: Adam Gilmore
>
> Partition pruning still tries to read Parquet files during the planning stage
> even though they don't match the partition filter.
> For example, if there were an invalid Parquet file in a directory that should
> not be queried:
> {code}
> 0: jdbc:drill:zk=local> select sum(price) from dfs.tmp.purchases where dir0 =
> 1;
> Query failed: IllegalArgumentException: file:/tmp/purchases/4/0_0_0.parquet
> is not a Parquet file (too small)
> {code}
> The reason is that the partition pruning happens after the Parquet plugin
> tries to read the footer of each file.
> Ideally, partition pruning would happen first before the format plugin gets
> involved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
