You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Y Ethan Guo (Jira)" <ji...@apache.org> on 2024/12/09 18:52:00 UTC
[jira] [Commented] (HUDI-8356) Update incremental config name in DataSourceOptions
[ https://issues.apache.org/jira/browse/HUDI-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904253#comment-17904253 ]
Y Ethan Guo commented on HUDI-8356:
-----------------------------------
We discussed that we'll keep the "instant time" notion as it generally represents a point of time. In that sense, it can represent a requested time for incremental queries on 0.x tables (table version 6) and a completion time for incremental queries on 1.0 tables (table version 8). So there is no need to change the config naming; this also makes migration easier (no need to change existing config name if a user uses these configs for incremental queries).
> Update incremental config name in DataSourceOptions
> ---------------------------------------------------
>
> Key: HUDI-8356
> URL: https://issues.apache.org/jira/browse/HUDI-8356
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Shawn Chang
> Assignee: Y Ethan Guo
> Priority: Critical
> Fix For: 1.0.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> DataSourceReadOptions.BEGIN_INSTANTTIME/END_INSTANTTIME would begin to use completion time instead of instant time after Hudi 1.0. We should update the config name to match the new behavior
--
This message was sent by Atlassian Jira
(v8.20.10#820010)