[
https://issues.apache.org/jira/browse/HUDI-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HUDI-7905:
------------------------------
Description: Currently, we use replacecommit for clustering, insert
overwrite and delete partition. Clustering should be a separate action for
requested and inflight instant. This simplifies a few things such as we do not
need to scan the replacecommit.requested to determine whether we are looking at
clustering plan or not. This would simplify the usage of pending clustering
related APIs. (was: Currently, we use replacecommit for clustering, insert
overwrite and delete partition. Clustering should be a separate action. This
simplifies a few things such as we do not need to scan the
replacecommit.requested to determine whether we are looking at clustering plan
or not. This also standardizes the usage of replacecommit to some extent
(related to HUDI-1739).)
> Use cluster action for clustering pending instants
> --------------------------------------------------
>
> Key: HUDI-7905
> URL: https://issues.apache.org/jira/browse/HUDI-7905
> Project: Apache Hudi
> Issue Type: Task
> Reporter: Sagar Sumit
> Assignee: Lokesh Jain
> Priority: Major
> Fix For: 1.0.0
>
>
> Currently, we use replacecommit for clustering, insert overwrite and delete
> partition. Clustering should be a separate action for requested and inflight
> instant. This simplifies a few things such as we do not need to scan the
> replacecommit.requested to determine whether we are looking at clustering
> plan or not. This would simplify the usage of pending clustering related
> APIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
