[ 
https://issues.apache.org/jira/browse/HIVE-25521?focusedWorklogId=661128&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-661128
 ]

ASF GitHub Bot logged work on HIVE-25521:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Oct/21 18:55
            Start Date: 06/Oct/21 18:55
    Worklog Time Spent: 10m 
      Work Description: harishjp commented on pull request #2639:
URL: https://github.com/apache/hive/pull/2639#issuecomment-936904970


   Thanks Panos. I've updated the code with review comments, please take a look.


-- 
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: gitbox-unsubscr...@hive.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 661128)
    Time Spent: 1h  (was: 50m)

> Data corruption when concatenating files with different compressions in same 
> table/partition
> --------------------------------------------------------------------------------------------
>
>                 Key: HIVE-25521
>                 URL: https://issues.apache.org/jira/browse/HIVE-25521
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Harish JP
>            Assignee: Harish JP
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently if files of different compressions are in same directory then 
> concatenate can fail and cause data corruption. This happens because file can 
> be moved by one task as incompatible file and the other tasks will fail after 
> this.
>  
> This issue is addressed in this Jira by only processing a file in one task 
> where offset 0 is process and ignoring the the file in all other tasks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to