Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 18 May 2016 23:21:12 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12736228.1408760929000.230219.1463613672833@Atlassian.JIRA>
In-Reply-To: <JIRA.12736228.1408760929000@Atlassian.JIRA>
References: <JIRA.12736228.1408760929000@Atlassian.JIRA> <JIRA.12736228.1408760929560@arcas>
Subject: [jira] [Commented] (DRILL-1328) Support table statistics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 May 2016 23:21:14 -0000


    [ https://issues.apache.org/jira/browse/DRILL-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15290075#comment-15290075 ] 

ASF GitHub Bot commented on DRILL-1328:
---------------------------------------

Github user vkorukanti commented on the pull request:

    https://github.com/apache/drill/pull/425#issuecomment-220186692
  
    Just want to clarify. There are TODOs and somethings may not work in certain cases. Consider this patch as alpha feature. Needs more work to make it a full fledged feature.


> Support table statistics
> ------------------------
>
>                 Key: DRILL-1328
>                 URL: https://issues.apache.org/jira/browse/DRILL-1328
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Cliff Buchanan
>             Fix For: Future
>
>         Attachments: 0001-PRE-Set-value-count-in-splitAndTransfer.patch
>
>
> This consists of several subtasks
> * implement operators to generate statistics
> * add "analyze table" support to parser/planner
> * create a metadata provider to allow statistics to be used by optiq in planning optimization
> * implement statistics functions
> Right now, the bulk of this functionality is implemented, but it hasn't been rigorously tested and needs to have some definite answers for some of the parts "around the edges" (how analyze table figures out where the table statistics are located, how a table "append" should work in a read only file system)
> Also, here are a few known caveats:
> * table statistics are collected by creating a sql query based on the string path of the table. This should probably be done with a Table reference.
> * Case sensitivity for column statistics is probably iffy
> * Math for combining two column NDVs into a joint NDV should be checked.
> * Schema changes aren't really being considered yet.
> * adding getDrillTable is probably unnecessary; it might be better to do getTable().unwrap(DrillTable.class)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)