[
https://issues.apache.org/jira/browse/HIVE-15944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895683#comment-15895683
]
wan kun commented on HIVE-15944:
--------------------------------
[~ashutoshc] I find my test case is something special .
In semantic analyze stage ,the plan tree is :
````
TS[0]-FIL[17]-SEL[2]-LIM[3]-RS[4] -SEL[5]-LIM[6]-RS[11] -JOIN[14]-SEL[15]-FS[16]
TS[7]-FIL[18]-SEL[9]-RS[13] -JOIN[14]
````
but when it compile to MR jobs, hive will add FIL[19] and TS[20] between LIM[6]
and RS[11] operator.
The FIL[19] will get schema from LIM[6] which LIM[6] is not the right output
cols.
So,I think two way to solve this problem.
1. when generator MR jobs ,use if condition to get the right file sink schema.
2. update the LIM operator's schema in the semantic optimize operation.
Now I try to fix this bug by the first way .Do you have any better suggestions！
And the HIVE-15944.6.patch run error because "No space left on device”,can you
have a look at the output message.
Many thinks!
> The order of cols is error in ColumnPrunerReduceSinkProc because of sort
> operator
> ---------------------------------------------------------------------------------
>
> Key: HIVE-15944
> URL: https://issues.apache.org/jira/browse/HIVE-15944
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 1.1.0, 2.2.0
> Reporter: wan kun
> Assignee: wan kun
> Fix For: 2.2.0
>
> Attachments: HIVE-15944.1.patch,
> HIVE-15944.2-branch-1.1.1.path.erroroutput, HIVE-15944.3.patch,
> HIVE-15944.4-branch-1.1.1.patch, HIVE-15944.4.patch, HIVE-15944.5.patch,
> HIVE-15944.6.patch, HIVE-15944-branch-1.1.patch, HIVE-15944.patch,
> STAGE_DEPENDENCIES
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> If one sql have two job.
> job 1:The order of cols is updated in ColumnPrunerReduceSinkProc because of
> sort operator.
> job 2 will read error in map operation because the cols order is old.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
