[
https://issues.apache.org/jira/browse/HIVE-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069885#comment-13069885
]
Hudson commented on HIVE-2296:
------------------------------
Integrated in Hive-trunk-h0.21 #843 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/843/])
HIVE-2296. bad compressed file names from insert into (Franklin Hu via
Siying Dong)
sdong : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1149724
Files :
* /hive/trunk/ql/src/test/queries/clientpositive/insert_compressed.q
* /hive/trunk/ql/src/test/results/clientpositive/insert_compressed.q.out
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/metadata/Hive.java
> bad compressed file names from insert into
> ------------------------------------------
>
> Key: HIVE-2296
> URL: https://issues.apache.org/jira/browse/HIVE-2296
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Franklin Hu
> Assignee: Franklin Hu
> Fix For: 0.8.0
>
> Attachments: hive-2296.1.patch, hive-2296.2.patch
>
>
> When INSERT INTO is run on a table with compressed output
> (hive.exec.compress.output=true) and existing files in the table, it may copy
> the new files in bad file names:
> Before INSERT INTO:
> 000000_0.gz
> After INSERT INTO:
> 000000_0.gz
> 000000_0.gz_copy_1
> This causes corrupted output when doing a SELECT * on the table.
> Correct behavior should be to pick a valid filename such as:
> 000000_0_copy_1.gz
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
