[jira] [Updated] (IMPALA-12832) EventProcessor shouldn't stop for failures in single-table event

["Sai Hemanth Gantasala (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-12832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sai Hemanth Gantasala updated IMPALA-12832:
-------------------------------------------
    Fix Version/s: Impala 4.4.0

> EventProcessor shouldn't stop for failures in single-table event
> ----------------------------------------------------------------
>
>                 Key: IMPALA-12832
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12832
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>            Reporter: Quanlong Huang
>            Assignee: Venugopal Reddy K
>            Priority: Critical
>             Fix For: Impala 4.4.0
>
>
> EventProcessor goes into the ERROR/NEEDS_INVALIDATE state when it hits unexpected failures in processing an event. The cause are usually bugs. When it stops, all tables that need sync will be impacted. However, the event might just a single-table event (in contrast to multi-table events like RenameTable, DropDatabaseCascade, CommitTxn, AbortTxn). We can consider skipping the event and just invalidating the table.



--
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