You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jason Altekruse (JIRA)" <ji...@apache.org> on 2015/04/10 19:27:12 UTC
[jira] [Resolved] (DRILL-2173) Enable querying partition
information without reading all data
[ https://issues.apache.org/jira/browse/DRILL-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Altekruse resolved DRILL-2173.
------------------------------------
Resolution: Fixed
Fixed in af7a52beeaed565e243d2d54ba75337ab95b924d
> Enable querying partition information without reading all data
> --------------------------------------------------------------
>
> Key: DRILL-2173
> URL: https://issues.apache.org/jira/browse/DRILL-2173
> Project: Apache Drill
> Issue Type: New Feature
> Components: Query Planning & Optimization
> Affects Versions: 0.7.0
> Reporter: Jason Altekruse
> Assignee: Jason Altekruse
> Fix For: 0.9.0
>
> Attachments: Drill-2173-maxdir-with-pruning-feb-27.patch, Drill-2173-maxdir-with-pruning-feb-6.patch, Drill-2173-partition-queries-with-pruning.patch
>
>
> When reading a series of files in nested directories, Drill currently adds columns representing the directory structure that was traversed to reach the file currently being read. These columns are stored as varchar under tha names dir0, dir1, ... As these are just regular columns, Drill allows arbitrary queries against this data, in terms of aggregates, filter, sort, etc. To allow optimizing reads, basic partition pruning has already been added to prune in the case of an expression like dir0 = "2015" or a simple in list, which is converted during planning to a series of ORs of equals expressions. If users want to query the directory information dynamically, and not include specific directory names in the query, this will prompt a full table scan and filter operation on the dir columns. This enhancement is to allow more complex queries to be run against directory metadata, and only scanning the matching directories.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)