You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2022/11/04 15:03:00 UTC

[jira] [Commented] (IMPALA-10656) Fire insert events before commit

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

Csaba Ringhofer commented on IMPALA-10656:
------------------------------------------

[~boroknagyz] oop, I don't know why this was not resolved for a year :)

> Fire insert events before commit
> --------------------------------
>
>                 Key: IMPALA-10656
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10656
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend, Frontend
>            Reporter: Csaba Ringhofer
>            Assignee: Csaba Ringhofer
>            Priority: Major
>
> Currently Impala commits an insert first, then reloads the table from HMS, and generates the insert events based on the difference between the two snapshots. (e.g. which file was not present in the old snapshot but are there in the new). Hive replication expects the insert events before the commit, so this may potentially lead to issues there,
> The solution is to collect the new files during the insert in the backend, and send the insert events based on this file set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org