[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar updated HUDI-1623:
-
Description:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Things need to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for regular instant time generation, we also need a lock (that we should
ship out by default)
was:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Things need to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for regular instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical
> increasing generation of the timestamp, for example, maybe hold a mutex lock
> with the last generated timestamp backing up there. Say it may holds a lock
> {*}L1{*}. For each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Things need to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for regular instant time generation, we also need a lock (that we should
> ship out by default)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-1623:
-
Description:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Things need to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for regular instant time generation, we also need a lock.
was:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for regular instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical
> increasing generation of the timestamp, for example, maybe hold a mutex lock
> with the last generated timestamp backing up there. Say it may holds a lock
> {*}L1{*}. For each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Things need to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for regular instant time generation, we also need a lock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-1623:
-
Description:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for regular instant time generation, we also need a lock.
was:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical
> increasing generation of the timestamp, for example, maybe hold a mutex lock
> with the last generated timestamp backing up there. Say it may holds a lock
> {*}L1{*}. For each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Something to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for regular instant time generation, we also need a lock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-1623:
-
Description:
We suggest a new file naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
was:
We suggest a new file format naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical
> increasing generation of the timestamp, for example, maybe hold a mutex lock
> with the last generated timestamp backing up there. Say it may holds a lock
> {*}L1{*}. For each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Something to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for normal instant time generation, we also need a lock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-1623:
-
Description:
We suggest a new file format naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical
increasing generation of the timestamp, for example, maybe hold a mutex lock
with the last generated timestamp backing up there. Say it may holds a lock
{*}L1{*}. For each instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
was:
We suggest a new file format naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical **
generation of the timestamp, for example, maybe hold a mutex lock with the last
generated timestamp backing up. Say it may holds a lock {*}L1{*}. For each
instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file format naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical
> increasing generation of the timestamp, for example, maybe hold a mutex lock
> with the last generated timestamp backing up there. Say it may holds a lock
> {*}L1{*}. For each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Something to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for normal instant time generation, we also need a lock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[
https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen updated HUDI-1623:
-
Description:
We suggest a new file format naming for the *completed* metadata file:
${start_time}.${action}.${completion_time}
We also need a global *Time Generator* that can ensure the monotonical **
generation of the timestamp, for example, maybe hold a mutex lock with the last
generated timestamp backing up. Say it may holds a lock {*}L1{*}. For each
instant time generation, it needs guard from the lock.
Before creating the completed file, we also need a lock guard from L1.
Something to note:
1. we only add completion timestamp to the completed metadata file;
2. we only add lock guard to the completed metadata file creation, not the
whole commiting procedure;
3. for normal instant time generation, we also need a lock.
> Support start_commit_time & end_commit_times for serializable incremental pull
> --
>
> Key: HUDI-1623
> URL: https://issues.apache.org/jira/browse/HUDI-1623
> Project: Apache Hudi
> Issue Type: Improvement
> Components: Common Core
>Reporter: Nishith Agarwal
>Assignee: Danny Chen
>Priority: Critical
> Fix For: 1.0.0
>
>
> We suggest a new file format naming for the *completed* metadata file:
> ${start_time}.${action}.${completion_time}
>
> We also need a global *Time Generator* that can ensure the monotonical **
> generation of the timestamp, for example, maybe hold a mutex lock with the
> last generated timestamp backing up. Say it may holds a lock {*}L1{*}. For
> each instant time generation, it needs guard from the lock.
>
> Before creating the completed file, we also need a lock guard from L1.
>
> Something to note:
> 1. we only add completion timestamp to the completed metadata file;
> 2. we only add lock guard to the completed metadata file creation, not the
> whole commiting procedure;
> 3. for normal instant time generation, we also need a lock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen updated HUDI-1623: - Reviewers: Vinoth Chandar > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Improvement > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Danny Chen >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Status: In Progress (was: Open) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Improvement > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Danny Chen >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Parent: (was: HUDI-6242) Issue Type: Improvement (was: Sub-task) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Improvement > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Epic Link: HUDI-6242 > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Improvement > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Parent: HUDI-6242 Issue Type: Sub-task (was: New Feature) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Sub-task > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Epic Link: (was: HUDI-1456) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: Sub-task > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Sprint: (was: 2022/08/22) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Sumit updated HUDI-1623: -- Fix Version/s: 0.12.1 (was: 0.12.0) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 0.12.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sagar Sumit updated HUDI-1623: -- Priority: Critical (was: Blocker) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Critical > Fix For: 0.12.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Epic Link: HUDI-1456 > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.12.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Fix Version/s: 0.12.0 (was: 0.11.0) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.12.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Sprint: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22, Hudi-Sprint-Mar-01, Hudi-Sprint-Mar-07, Hudi-Sprint-Mar-14 (was: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22, Hudi-Sprint-Mar-01, Hudi-Sprint-Mar-07) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Sprint: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22, Hudi-Sprint-Mar-01, Hudi-Sprint-Mar-07 (was: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22, Hudi-Sprint-Mar-01) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Story Points: 5 > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Xu updated HUDI-1623: - Sprint: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22, Hudi-Sprint-Mar-01 (was: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Mahindra updated HUDI-1623: -- Sprint: Hudi-Sprint-Feb-14, Hudi-Sprint-Feb-22 (was: Hudi-Sprint-Feb-14) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Sprint: Hudi-Sprint-Feb-14 > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Vinoth Chandar >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Priority: Blocker (was: Major) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: sivabalan narayanan >Priority: Blocker > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Chen updated HUDI-1623: - Fix Version/s: (was: 0.10.0) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: sivabalan narayanan >Priority: Major > Fix For: 0.11.0 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sivabalan narayanan updated HUDI-1623: -- Priority: Major (was: Blocker) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: sivabalan narayanan >Priority: Major > Fix For: 0.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sivabalan narayanan updated HUDI-1623: -- Status: In Progress (was: Open) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: sivabalan narayanan >Priority: Blocker > Fix For: 0.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-1623: - Priority: Blocker (was: Major) > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Nishith Agarwal >Priority: Blocker > Fix For: 0.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-1623) Support start_commit_time & end_commit_times for serializable incremental pull
[ https://issues.apache.org/jira/browse/HUDI-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishith Agarwal updated HUDI-1623: -- Fix Version/s: 0.10.0 > Support start_commit_time & end_commit_times for serializable incremental pull > -- > > Key: HUDI-1623 > URL: https://issues.apache.org/jira/browse/HUDI-1623 > Project: Apache Hudi > Issue Type: New Feature > Components: Common Core >Reporter: Nishith Agarwal >Assignee: Nishith Agarwal >Priority: Major > Fix For: 0.10.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
