[
https://issues.apache.org/jira/browse/HUDI-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kate Huber updated HUDI-7527:
-----------------------------
Sprint: Sprint 2024-03-25, Sprint 2024-04-26, 2024/06/17-30, 2024/06/03-16,
Hudi 1.0 Sprint2024/10/7-10/13 (was: Sprint 2024-03-25, Sprint 2024-04-26,
2024/06/17-30, 2024/06/03-16)
> Include instants outside commits and compaction for generating the latest
> instant and timeline hash for timeline server requests
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: HUDI-7527
> URL: https://issues.apache.org/jira/browse/HUDI-7527
> Project: Apache Hudi
> Issue Type: Bug
> Components: table-service, timeline-server
> Reporter: Ethan Guo (this is the old account; please use "yihua")
> Assignee: Ethan Guo (this is the old account; please use "yihua")
> Priority: Blocker
> Fix For: 1.0.0
>
>
> When the write client sends the request to the timeline server with the
> latest instant and timeline hash, the latest instant and timeline hash are
> based on the filtered timeline that does not contain pending log compaction
> or clustering (replacecommit). In such a case, consecutive async scheduling
> of clustering, even with a newly instantiated write client, does not trigger
> FSV refresh at the timeline server; but FSV is affected by pending clustering
> and log compaction (e.g., fgIdToPendingLogCompaction, fgIdToReplaceInstants,
> fgIdToPendingClustering).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
