[
https://issues.apache.org/jira/browse/HUDI-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Y Ethan Guo updated HUDI-8576:
------------------------------
Description:
[https://github.com/apache/hudi/pull/12323#discussion_r1857401875]
We should still remove
{code:java}
if (hasLogFiles) {
params.put("hoodie.datasource.query.type", "snapshot");
} else {
params.put("hoodie.datasource.query.type", "read_optimized");
} {code}
after we switched clustering execution to use the new parquet file format and
file group reader in Spark, so there is no performance caveat between snapshot
and read-optimized queries in the legacy relation-based reader path in Spark.
> Use new file format instead of relations for clustering execution
> -----------------------------------------------------------------
>
> Key: HUDI-8576
> URL: https://issues.apache.org/jira/browse/HUDI-8576
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Y Ethan Guo
> Priority: Blocker
> Fix For: 1.1.0
>
>
> [https://github.com/apache/hudi/pull/12323#discussion_r1857401875]
> We should still remove
> {code:java}
> if (hasLogFiles) {
> params.put("hoodie.datasource.query.type", "snapshot");
> } else {
> params.put("hoodie.datasource.query.type", "read_optimized");
> } {code}
> after we switched clustering execution to use the new parquet file format and
> file group reader in Spark, so there is no performance caveat between
> snapshot and read-optimized queries in the legacy relation-based reader path
> in Spark.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
