dengzhhu653 opened a new pull request, #4479:
URL: https://github.com/apache/hive/pull/4479

   …es in union all
   
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: 
https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a 
faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other 
DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   
   
   ### Why are the changes needed?
   Think of an union all case inserting data to an external table(dynamic 
partition):
   FS[1] specPath: <staging_dir>/-ext-10000/HIVE_UNION_SUBDIR_1
   FS[2] specPath: <staging_dir>/-ext-10000/HIVE_UNION_SUBDIR_2
   
   Finally, the output of FS will locate under the directory:
   FS[1]: <staging_dir>/_tmp.-ext-10000/<dynamic_partition>/HIVE_UNION_SUBDIR_1
   FS[2]: <staging_dir>/_tmp.-ext-10000/<dynamic_partition>/HIVE_UNION_SUBDIR_2
   
   When the task finishes, FS[1] and FS[2] will call jobClose to move their 
output to <staging_dir>/-ext-10000, the MoveTask is responsible for moving it 
to the destination table.
   
   
https://github.com/apache/hive/blob/81759a105e50b9fd8c66ffbf2920f425a1d7a64c/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/TezTask.java#L679-L689
   
   Before the FS[1] moves the data, it will rename 
<staging_dir>/_tmp.-ext-10000 to <staging_dir>/_tmp.-ext-10000.moved, 
   
https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java#L1453-L1456
   
   FS[1] will only deduplicate the result under the 
_tmp.-ext-10000.moved/<dynamic_partition>/HIVE_UNION_SUBDIR_1, and add the 
valid output file to `filesKept`, ignore the result under HIVE_UNION_SUBDIR_2 
or more...
   When it turns to FS[2] to close the operator, as the temp output directory 
has already been renamed to `_tmp.-ext-10000.moved`, so the FS[2] will do 
nothing.
   
   So this will cause task result duplication, and in some cases, the result 
will lose as the `filesKept` only keeps the result of only one branch.
   
   To solve this, one idea is making every FS have his own private temp output 
directory. For example:
   FS[1]: 
<staging_dir>/-ext-10000/_tmp.HIVE_UNION_SUBDIR_1/<dynamic_partition>/HIVE_UNION_SUBDIR_1
   FS[2]: 
<staging_dir>/-ext-10000/_tmp.HIVE_UNION_SUBDIR_2/<dynamic_partition>/HIVE_UNION_SUBDIR_2
   
   When FS closes, each FS operator only takes care of his own output, and move 
the temp output to <staging_dir>/-ext-10000 as it does before, and this method 
will bring some performance gain in case renaming to `_tmp.-ext-10000.moved` is 
not allowed:
   
https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java#L1461-L1462
   
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   
   
   ### Does this PR introduce _any_ user-facing change?
   No
   <!--
   Note that it means *any* user-facing change including all aspects such as 
the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description, screenshot and/or a reproducable 
example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released Hive versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   
   ### Is the change a dependency upgrade?
   No
   <!--
   If yes, please attach a file with output from mvn dependency:tree to 
validate a complete upgrade of dependency.
   If no, write 'No'.
   -->
   
   
   ### How was this patch tested?
   Added UT
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to