Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98317189AD for ; Sun, 18 Oct 2015 20:05:05 +0000 (UTC) Received: (qmail 89007 invoked by uid 500); 18 Oct 2015 20:05:05 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 88835 invoked by uid 500); 18 Oct 2015 20:05:05 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 88395 invoked by uid 99); 18 Oct 2015 20:05:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Oct 2015 20:05:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 04ED92C0451 for ; Sun, 18 Oct 2015 20:05:05 +0000 (UTC) Date: Sun, 18 Oct 2015 20:05:05 +0000 (UTC) From: "Aman Sinha (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-3948) Partitioning columns of a Parquet table should be made visible to end user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Aman Sinha created DRILL-3948: --------------------------------- Summary: Partitioning columns of a Parquet table should be made visible to end user Key: DRILL-3948 URL: https://issues.apache.org/jira/browse/DRILL-3948 Project: Apache Drill Issue Type: Improvement Components: Metadata, Query Planning & Optimization Affects Versions: 1.2.0 Reporter: Aman Sinha For Parquet files, Drill can do partition pruning for filter conditions on a column which satisfies the following criteria: Each parquet file has a single value of that column. The parquet metadata is examined for the min and max values of that column and if they are the same, the column is considered a partitioning column. When CTAS auto-partition is used, the above criteria is enforced, but even for files created through external methods could satisfy the criteria. It is difficult for users to know what exactly are the candidate partitioning columns in the table. We should provide this information in a user friendly way: for instance: - special 'show partition columns for ' command - In the Explain plan, show partition columns for the table in Scan node More options should be discussed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)