[
https://issues.apache.org/jira/browse/HUDI-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374790#comment-17374790
]
ASF GitHub Bot commented on HUDI-1468:
--------------------------------------
codope commented on pull request #3211:
URL: https://github.com/apache/hudi/pull/3211#issuecomment-874070580
@satishkotha Couple of high level questions:
* Would preserving commit time be sufficient to support incremental read?
Won't we need incremental timeline support (#2388 ) as well?
* I see that a new `SparkAllowUpdateStrategy` has been added. How are we
handling update conflicts?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@hudi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> incremental read support with clustering
> ----------------------------------------
>
> Key: HUDI-1468
> URL: https://issues.apache.org/jira/browse/HUDI-1468
> Project: Apache Hudi
> Issue Type: Sub-task
> Components: Incremental Pull
> Affects Versions: 0.9.0
> Reporter: satish
> Assignee: liwei
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> As part of clustering, metadata such as hoodie_commit_time changes for
> records that are clustered. This is specific to
> SparkBulkInsertBasedRunClusteringStrategy implementation. Figure out a way to
> carry commit_time from original record to support incremental queries.
> Also, incremental queries dont work with 'replacecommit' used by clustering
> HUDI-1264. Change incremental query to work for replacecommits created by
> Clustering.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
