[jira] [Resolved] (IMPALA-10923) Fine grained table refreshing at partition level events for transactional tables

["Yu-Wen Lai (Jira)" <ji...@apache.org>]

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

Yu-Wen Lai resolved IMPALA-10923.
---------------------------------
     Fix Version/s: Impala 4.1.0
    Target Version: Impala 4.1.0
        Resolution: Fixed

> Fine grained table refreshing at partition level events for transactional tables
> --------------------------------------------------------------------------------
>
>                 Key: IMPALA-10923
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10923
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>            Reporter: Yu-Wen Lai
>            Assignee: Yu-Wen Lai
>            Priority: Major
>             Fix For: Impala 4.1.0
>
>
> For ensuring the transactional tables are consistent, we currently take whole table refreshing even a change is just for a partition only. That is too expensive and possibly make event processing has a longer delay.
> To enable fine-grained table refreshing, there are three main changes in this proposal.
>  # maintain validWriteIdList in Catalogd for transactional tables. We will track write id changes by AllocWriteIdEvents, CommitTxnEvents, and AbortTxnEvents.
>  # trigger partition level refreshing for addPartitionEvents, dropPartitionEvents, and AlterPartitionEvents.
>  # Introduce a config *incremental_refresh_acid*, which can switch on/off the fine-grained table refreshing



--
This message was sent by Atlassian Jira
(v8.20.1#820001)