You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sungpeo Kook (JIRA)" <ji...@apache.org> on 2019/07/12 03:14:00 UTC
[jira] [Commented] (HIVE-20410) aborted Insert Overwrite on
transactional table causes "Not enough history available for..." error
[ https://issues.apache.org/jira/browse/HIVE-20410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883494#comment-16883494 ]
Sungpeo Kook commented on HIVE-20410:
-------------------------------------
I want to use `insert overwrite` on Hive 3.x.
Is there any reason why this patch couldn't be committed to branch-3 ?
> aborted Insert Overwrite on transactional table causes "Not enough history available for..." error
> --------------------------------------------------------------------------------------------------
>
> Key: HIVE-20410
> URL: https://issues.apache.org/jira/browse/HIVE-20410
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-20410.01.patch, HIVE-20410.02.patch
>
>
> suppose
> insert overwrite T values(1)
> is aborted.
> this creates a base_x directory (for insert-only transactional tables currently and for full CRUD once 'rename' in the MoveTask is eliminated) but subsequent read fails with "Not enough history available for..." error.
> The problem is that the logic to produce this exception finds this base_x but treats it as if it was produced by a compactor, in which case the error would'v been appropriate.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)