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

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

GitHub user mehant opened a pull request:

    https://github.com/apache/drill/pull/231

    DRILL-3634: Add number of partitions information in the plan for hive…

    … scans

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mehant/drill DRILL-3634_1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/231.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #231
    
----
commit 2ce3d96e824eca8a17e15509d2cf78b7e07ac471
Author: Mehant Baid <[email protected]>
Date:   2015-10-29T22:10:12Z

    DRILL-3634: Add number of partitions information in the plan for hive scans

----


> Hive Scan : Add fileCount (no of files scanned) or no of partitions scanned 
> to the text plan
> --------------------------------------------------------------------------------------------
>
>                 Key: DRILL-3634
>                 URL: https://issues.apache.org/jira/browse/DRILL-3634
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Hive
>    Affects Versions: 1.2.0
>            Reporter: Rahul Challapalli
>             Fix For: Future
>
>
> The hive scan portion of the text plan only lists the files scanned. It would 
> be helpful if the text plan also had fileCount value or the number of 
> partitions scanned.
> Reason : Currently as part of our tests we are verifying plans using a regex 
> based verification and the expected regex is matching more than it should. 
> Fixing this might be hard. So if we have the fileCount/partitionCount as part 
> of the plan, the plan comparision will be more accurate



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

Reply via email to