You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "voonhous (via GitHub)" <gi...@apache.org> on 2026/10/28 11:33:34 UTC

[PR] fix(spark): reject collation-changing casts in data skipping [hudi]

voonhous opened a new pull request, #20458:
URL: https://github.com/apache/hudi/pull/20458

   ### Describe the issue this Pull Request addresses
   
   Refs #19445 (split out of #19475)
   
   On Spark 4 `StringType` carries a collation. `isCastPreservingOrdering` matched `String <-> Numeric` against the `StringType` companion, which only equals the default collation, so every cast involving a collated string fell through to `case _ => true`. A cast to another collation changes the sort order: stats `["B", "a"]` are in UTF8_BINARY order, but `CAST(b AS STRING COLLATE UTF8_LCASE) = 'a'` translates to `"B" <= "a"` in UTF8_LCASE, which is false, so a file holding `"a"` is pruned.
   
   ### Summary and Changelog
   
   - `HoodieSparkTypeUtils.isCastPreservingOrdering`: the `String <-> Numeric` arms match by type, so collated strings are rejected too; `string -> string` casts require an identical `StringType`. On Spark 3 `StringType` is a singleton, so nothing changes there.
   - Tests: `TestHoodieCatalystExpressionUtils` covers collation-changing, collated-to-numeric and collation-preserving casts; `TestDataSkippingUtils` adds the repro above. Both are skipped on Spark 3 profiles, since collation APIs only exist on Spark 4.
   
   ### Impact
   
   No public API change. Filters over collation-changing casts no longer prune. Spark 4 `StringType` equality also compares the char/varchar length constraint, so casts between `CHAR`/`VARCHAR` and `STRING` (seen only with `spark.sql.preserveCharVarcharTypeInfo`) also stop pruning.
   
   ### Risk Level
   
   low. Every newly rejected cast falls back to no pruning.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   


-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "voonhous (via GitHub) via commits" <co...@hudi.apache.org>.
voonhous merged PR #20458:
URL: https://github.com/apache/hudi/pull/20458


-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "voonhous (via GitHub) via commits" <co...@hudi.apache.org>.
voonhous commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4453198509


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -36,9 +36,18 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: In the casting rules defined by Spark, only casting from String to Numeric
-      // (and vice versa) are the only casts that might break the ordering of the elements after casting
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      // (and vice versa) are the only casts that might break the ordering of the elements after casting.
+      // These match by type, so that collated strings on Spark 4 are rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr
+      // NOTE: Every type casts to a string, so collated targets are rejected whatever the source
+      //       (for ex, binary bounds are in byte order, which UTF8_LCASE does not follow)
+      case (_, toStr: StringType) => toStr == StringType
 
       case _ => true

Review Comment:
   Fixed in e8f4150: any cast from a collated string to a non-string type (binary, date, ...) is now rejected. The new assertions in `testCollationChangingStringCastsDoNotPreserveOrdering` fail without the fix.
   



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "nsivabalan (via GitHub) via commits" <co...@hudi.apache.org>.
nsivabalan commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4460923444


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -37,16 +37,29 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: Casting between String and Numeric types re-orders elements (for ex, "10" < "9"
-      //       lexicographically)
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      //       lexicographically). These match by type, so that collated strings on Spark 4 are
+      //       rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
       // NOTE: Timestamps format in the session time zone, so local time repeats across a DST
       //       fall-back (for ex, 01:30 EDT is followed by 01:10 EST) and the strings re-order
-      case (TimestampType, StringType) => false
+      case (TimestampType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr

Review Comment:
   This covers a collation introduced by a cast. What about a column declared `STRING COLLATE UTF8_LCASE` and filtered with no cast, e.g. `col = 'a'`? I don't see collation handling anywhere in data skipping, so I'd expect the column stats bounds to be computed in byte order, while the index's min/max columns take the table schema's collated type and get compared under `UTF8_LCASE`. That would give the same wrong pruning as the repro here. Traced from source, not run. If it holds, it needs a follow-up issue (or skipping data skipping for columns with a non-default collation).



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "voonhous (via GitHub) via commits" <co...@hudi.apache.org>.
voonhous commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4462705628


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -37,16 +37,29 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: Casting between String and Numeric types re-orders elements (for ex, "10" < "9"
-      //       lexicographically)
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      //       lexicographically). These match by type, so that collated strings on Spark 4 are
+      //       rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
       // NOTE: Timestamps format in the session time zone, so local time repeats across a DST
       //       fall-back (for ex, 01:30 EDT is followed by 01:10 EST) and the strings re-order
-      case (TimestampType, StringType) => false
+      case (TimestampType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr

Review Comment:
   Not reachable today: Hudi rejects collated string columns at schema conversion, so `CREATE TABLE ... name STRING COLLATE UTF8_LCASE USING hudi` and a DataFrame write with a collated column both fail before any stats are written:
   
   ```
   IncompatibleSchemaException: Unexpected Spark DataType: StringType(UTF8_LCASE)
     at HoodieSparkSchemaConverters.toHoodieTypeNested
   ```
   
   The mechanism is real though: Spark 4.1 still hands `col = 'a'` on a collated column to `HoodieFileIndex`, so data skipping needs a collation guard before the converter accepts collations. Added that to the #19445 checklist.
   



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "wombatu-kun (via GitHub)" <gi...@apache.org>.
wombatu-kun commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4408081760


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -36,9 +36,15 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: In the casting rules defined by Spark, only casting from String to Numeric
-      // (and vice versa) are the only casts that might break the ordering of the elements after casting
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      // (and vice versa) are the only casts that might break the ordering of the elements after casting.
+      // These match by type, so that collated strings on Spark 4 are rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr

Review Comment:
   A binary column cast directly to a collated string (`CAST(bin AS STRING COLLATE UTF8_LCASE) = 'a'`) still falls through to `case _ => true`, and column stats V2 indexes binary columns, so its byte-ordered bounds get compared in UTF8_LCASE just like in the repro. Should `(BinaryType, toStr: StringType)` also be rejected unless `toStr == StringType`?



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "shangxinli (via GitHub) via commits" <co...@hudi.apache.org>.
shangxinli commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4433899802


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -36,9 +36,18 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: In the casting rules defined by Spark, only casting from String to Numeric
-      // (and vice versa) are the only casts that might break the ordering of the elements after casting
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      // (and vice versa) are the only casts that might break the ordering of the elements after casting.
+      // These match by type, so that collated strings on Spark 4 are rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr
+      // NOTE: Every type casts to a string, so collated targets are rejected whatever the source
+      //       (for ex, binary bounds are in byte order, which UTF8_LCASE does not follow)
+      case (_, toStr: StringType) => toStr == StringType
 
       case _ => true

Review Comment:
   This still falls through to true for a collated StringType cast to a non-string type, like BinaryType -- binary bounds are byte-ordered, which UTF8_LCASE doesn't follow.



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "voonhous (via GitHub)" <gi...@apache.org>.
voonhous commented on code in PR #20458:
URL: https://github.com/apache/hudi/pull/20458#discussion_r4420375191


##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/HoodieSparkTypeUtils.scala:
##########
@@ -36,9 +36,15 @@ object HoodieSparkTypeUtils {
   def isCastPreservingOrdering(from: DataType, to: DataType): Boolean =
     (from, to) match {
       // NOTE: In the casting rules defined by Spark, only casting from String to Numeric
-      // (and vice versa) are the only casts that might break the ordering of the elements after casting
-      case (StringType, _: NumericType) => false
-      case (_: NumericType, StringType) => false
+      // (and vice versa) are the only casts that might break the ordering of the elements after casting.
+      // These match by type, so that collated strings on Spark 4 are rejected as well
+      case (_: StringType, _: NumericType) => false
+      case (_: NumericType, _: StringType) => false
+      // NOTE: On Spark 4 StringType carries a collation, and casting to a different collation changes
+      //       the sort order (for ex, "B" < "a" in UTF8_BINARY but "a" < "B" in UTF8_LCASE). Equality
+      //       also compares the char/varchar length constraint, so those casts are conservatively
+      //       rejected too. On Spark 3 StringType is a singleton, making this arm trivially true
+      case (fromStr: StringType, toStr: StringType) => fromStr == toStr

Review Comment:
   Yes, fixed in 79c5c0d7e2fb, and by target rather than by source: every type casts to a string, so any cast into a non-default `StringType` is now rejected (binary, date, timestamp, ...), not only `string -> string`. Added binary and date cases to the collation unit test.



-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] fix(spark): reject collation-changing casts in data skipping [hudi]

Posted by "codecov-commenter (via GitHub)" <gi...@apache.org>.
codecov-commenter commented on PR #20458:
URL: https://github.com/apache/hudi/pull/20458#issuecomment-6468209689

   ## [Codecov](https://app.codecov.io/gh/apache/hudi/pull/20458?dropdown=coverage&src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) Report
   :white_check_mark: All modified and coverable lines are covered by tests.
   :white_check_mark: Project coverage is 80.82%. Comparing base ([`82d724b`](https://app.codecov.io/gh/apache/hudi/commit/82d724b93b552b822a968ba4cbc7fdf3360c4ccb?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)) to head ([`cfd272a`](https://app.codecov.io/gh/apache/hudi/commit/cfd272ad67bd2b3e494fcd1857b5abb2e21ebad1?dropdown=coverage&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)).
   :warning: Report is 1 commits behind head on master.
   
   <details><summary>Additional details and impacted files</summary>
   
   
   
   ```diff
   @@             Coverage Diff              @@
   ##             master   #20458      +/-   ##
   ============================================
   - Coverage     80.82%   80.82%   -0.01%     
   + Complexity    36028    36027       -1     
   ============================================
     Files          2575     2575              
     Lines        147258   147256       -2     
     Branches      18097    18095       -2     
   ============================================
   - Hits         119020   119018       -2     
   - Misses        20035    20036       +1     
   + Partials       8203     8202       -1     
   ```
   
   | [Components](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=components&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
   |---|---|---|
   | [hudi-common](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `84.18% <ø> (-0.01%)` | :arrow_down: |
   | [hudi-client](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `84.03% <ø> (ø)` | |
   | [hudi-flink](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `86.16% <ø> (ø)` | |
   | [hudi-spark-datasource](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `74.19% <ø> (+<0.01%)` | :arrow_up: |
   | [hudi-utilities](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `79.26% <ø> (ø)` | |
   | [hudi-cli](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `70.80% <ø> (ø)` | |
   | [hudi-hadoop](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `71.18% <ø> (ø)` | |
   | [hudi-sync](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `77.31% <ø> (ø)` | |
   | [hudi-io](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `81.57% <ø> (ø)` | |
   | [hudi-timeline-service](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `83.41% <ø> (ø)` | |
   | [hudi-cloud](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `81.01% <ø> (ø)` | |
   | [hudi-kafka-connect](https://app.codecov.io/gh/apache/hudi/pull/20458/components?src=pr&el=component&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `57.90% <ø> (ø)` | |
   
   | [Flag](https://app.codecov.io/gh/apache/hudi/pull/20458/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
   |---|---|---|
   | [hadoop-mr-java-client](https://app.codecov.io/gh/apache/hudi/pull/20458/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | `43.93% <ø> (-0.01%)` | :arrow_down: |
   
   Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#carryforward-flags-in-the-pull-request-comment) to find out more.
   
   | [Files with missing lines](https://app.codecov.io/gh/apache/hudi/pull/20458?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache) | Coverage Δ | |
   |---|---|---|
   | [...la/org/apache/spark/sql/HoodieSparkTypeUtils.scala](https://app.codecov.io/gh/apache/hudi/pull/20458?src=pr&el=tree&filepath=hudi-spark-datasource%2Fhudi-spark-common%2Fsrc%2Fmain%2Fscala%2Forg%2Fapache%2Fspark%2Fsql%2FHoodieSparkTypeUtils.scala&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache#diff-aHVkaS1zcGFyay1kYXRhc291cmNlL2h1ZGktc3BhcmstY29tbW9uL3NyYy9tYWluL3NjYWxhL29yZy9hcGFjaGUvc3Bhcmsvc3FsL0hvb2RpZVNwYXJrVHlwZVV0aWxzLnNjYWxh) | `60.00% <ø> (+17.14%)` | :arrow_up: |
   
   ... and [1 file with indirect coverage changes](https://app.codecov.io/gh/apache/hudi/pull/20458/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=apache)
   </details>
   <details><summary> :rocket: New features to boost your workflow: </summary>
   
   - :snowflake: [Test Analytics](https://docs.codecov.com/docs/test-analytics): Detect flaky tests, report on failures, and find test suite problems.
   - :package: [JS Bundle Analysis](https://docs.codecov.com/docs/javascript-bundle-analysis): Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
   </details>


-- 
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-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org