You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Aman Sinha (JIRA)" <ji...@apache.org> on 2014/11/25 21:32:13 UTC

[jira] [Comment Edited] (DRILL-1742) Use Hive stats when planning queries on Hive data sources

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

Aman Sinha edited comment on DRILL-1742 at 11/25/14 8:31 PM:
-------------------------------------------------------------

Revised patch looks ok to me.  For future reference, could you pls add some comments here to indicate the types of tests we discussed: 
 1.  Initial table creation and no rows loaded - what was the expected behavior (since numRows property is not available)
 2.  Behavior after rows were loaded  
    a) before running analyze
    b) after running analyze
 3.  Tests with partition pruning - are we getting the reduced row count ?



was (Author: amansinha100):
Revised patch looks ok to me.  For future reference, could you pls add some comments here to indicate the types of tests we discussed: 
 1.  Initial table creation and no rows loaded - what was the expected behavior (since numRows property is not available)
 2.  Behavior after rows were loaded 
 3.  Tests with partition pruning - are we getting the reduced row count ?


> Use Hive stats when planning queries on Hive data sources
> ---------------------------------------------------------
>
>                 Key: DRILL-1742
>                 URL: https://issues.apache.org/jira/browse/DRILL-1742
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Query Planning & Optimization, Storage - Hive
>    Affects Versions: 0.6.0
>            Reporter: Venki Korukanti
>            Assignee: Deneche A. Hakim
>             Fix For: 0.7.0
>
>         Attachments: DRILL-1742.1.patch.txt, DRILL-1742.2.patch.txt, DRILL-1742.3.patch.txt, DRILL-1742.4.patch.txt
>
>




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