hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8966) Delta files created by hive hcatalog streaming cannot be compacted
Date Wed, 26 Nov 2014 22:55:13 GMT

    [ https://issues.apache.org/jira/browse/HIVE-8966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226943#comment-14226943
] 

Alan Gates commented on HIVE-8966:
----------------------------------

Ok, that makes sense.  You're current delta has the file because it's still open and being
written to.  It also explains why my tests don't see it, as they don't run long enough.  The
streaming is always done by the time the compactor kicks in.  Why don't you post a patch to
this JIRA with the change for 1, and I can get that committed.

[~hagleitn], I'd like to put this in 0.14.1 as well as trunk if you're ok with it, since it
blocks compaction for users using the streaming interface.

> Delta files created by hive hcatalog streaming cannot be compacted
> ------------------------------------------------------------------
>
>                 Key: HIVE-8966
>                 URL: https://issues.apache.org/jira/browse/HIVE-8966
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog
>    Affects Versions: 0.14.0
>         Environment: hive
>            Reporter: Jihong Liu
>            Assignee: Alan Gates
>            Priority: Critical
>
> hive hcatalog streaming will also create a file like bucket_n_flush_length in each delta
directory. Where "n" is the bucket number. But the compactor.CompactorMR think this file also
needs to compact. However this file of course cannot be compacted, so compactor.CompactorMR
will not continue to do the compaction. 
> Did a test, after removed the bucket_n_flush_length file, then the "alter table partition
compact" finished successfully. If don't delete that file, nothing will be compacted. 
> This is probably a very severity bug. Both 0.13 and 0.14 have this issue



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message