[ https://issues.apache.org/jira/browse/HIVE-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242133#comment-14242133 ]
Navis commented on HIVE-9076: ----------------------------- Test always makes file composition like below, {noformat} 000000_0 000000_0_copy_1 000000_0_copy_2 000000_0_copy_3 000000_0_copy_4 000000_0_copy_5 {noformat} The composition in description is caused by a bug which I've made (I'm in progress on HIVE-8814). But I think this should be fixed first. > incompatFileSet in AbstractFileMergeOperator should be marked to skip task id > check > ----------------------------------------------------------------------------------- > > Key: HIVE-9076 > URL: https://issues.apache.org/jira/browse/HIVE-9076 > Project: Hive > Issue Type: Bug > Components: Query Processor > Reporter: Navis > Assignee: Navis > Priority: Minor > Attachments: HIVE-9076.1.patch.txt > > > In some file composition, AbstractFileMergeOperator removes incompatible > files. For example, > {noformat} > 000000_0 (v12) > 000000_0_copy_1 (v12) > 000000_1 (v11) > 000000_1_copy_1 (v11) > 000000_1_copy_2 (v11) > 000000_2 (v12) > {noformat} > 000000_1 (v11) will be removed because 000000 is assigned to new merged file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)