[
https://issues.apache.org/jira/browse/HUDI-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangkang updated HUDI-6359:
---------------------------
Description:
If spark offline compaction execution fails, both a.compaction.requested and
a.compaction.inflight states exist at the same time, which will cause the next
offline compaction never rolledback for compaction plan a.compactino.requested.
Spark offline clustering is same as clustering.
was:If spark offline compaction execution fails, both a.compaction.requested
and a.compaction.inflight states exist at the same time, which will cause the
next offline compaction never rolledback for compaction plan
a.compactino.requested.
Summary: Spark offline compaction/clustering will never rollback when
both requested and inflight states exist (was: Spark offline compaction will
never rollback when both compaction.requested and compaction.inflight states
exist)
> Spark offline compaction/clustering will never rollback when both requested
> and inflight states exist
> -----------------------------------------------------------------------------------------------------
>
> Key: HUDI-6359
> URL: https://issues.apache.org/jira/browse/HUDI-6359
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: wangkang
> Priority: Major
> Fix For: 0.14.0
>
>
> If spark offline compaction execution fails, both a.compaction.requested and
> a.compaction.inflight states exist at the same time, which will cause the
> next offline compaction never rolledback for compaction plan
> a.compactino.requested.
> Spark offline clustering is same as clustering.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
