[
https://issues.apache.org/jira/browse/DRILL-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204967#comment-14204967
]
Rahul Challapalli commented on DRILL-1638:
------------------------------------------
It would be helpful if we can have all the inputsplits that are being scanned.
Something like the below example
{code}
inputSplits=[
maprfs:
/drill/testdata/partition_pruning/hive/text/lineitempart/1991/lineitemaa.tbl:
0+1187513,
maprfs:
/drill/testdata/partition_pruning/hive/text/lineitempart/1991/lineitemab.tbl:
0+1187513
]
{code}
And if the underlying table has partitions, it would also be helpful if we can
list the partitions. Something like the below example (hierarchical partitions)
{code}
partitions=[
{1991, Feb}, {1992, Jan}, {1992, Dec}.......
]
{code}
> Text plan should contain information about text partitions
> ----------------------------------------------------------
>
> Key: DRILL-1638
> URL: https://issues.apache.org/jira/browse/DRILL-1638
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Reporter: Ramana Inukonda Nagaraj
> Assignee: Hanifi Gunes
>
> An explain plan command for
> 0: jdbc:drill:> explain plan for select * from
> `/mapr/drill-stress/drill/testdata/text_storage/lineitempart/` where
> dir0=1993;
> results in a text plan which lacks the information that only dir0=1993 is
> scanned. The json plan has this information as below.
> 00-00 Screen
> 00-01 Project(*=[$0])
> 00-02 Scan(groupscan=[EasyGroupScan
> [selectionRoot=/mapr/drill-stress/drill/testdata/text_storage/lineitempart,
> numFiles=1, columns = [SchemaPath [`*`]]]])
> Information in json plan which should be in the text plan.
> "graph" : [ {
> "pop" : "fs-scan",
> "@id" : 2,
> "files" : [
> "/mapr/drill-stress/drill/testdata/text_storage/lineitempart/1993/lineitemac.tbl"
> ],
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
