You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Vinoth Chandar (Jira)" <ji...@apache.org> on 2021/05/21 20:52:00 UTC
[jira] [Commented] (HUDI-1739) Standardize usage of replacecommit
files across the code base
[ https://issues.apache.org/jira/browse/HUDI-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349474#comment-17349474 ]
Vinoth Chandar commented on HUDI-1739:
--------------------------------------
[~satishkotha] from the PR, it seems like we may not be generally adhering to some conventions for the replace commit? Can we use this Jira to flag these and see how to approach them? Or do you not see any gaps at all?
> Standardize usage of replacecommit files across the code base
> -------------------------------------------------------------
>
> Key: HUDI-1739
> URL: https://issues.apache.org/jira/browse/HUDI-1739
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Jagmeet Bali
> Assignee: Susu Dong
> Priority: Minor
> Labels: sev:high
>
> Fixes can be to
> # Ignore empty replacecommit.requested files.
> # Standardise the replacecommit.requested format across all invocations be it from clustering or this use case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)