You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[fix](external) Preserve Hudi and Paimon timestamp semantics
Issue Number: None
Related PR: #65446
Problem Summary:
Hudi scanner v2 started applying the Hive INT96 compatibility timezone, which changed Hudi existing session-timezone behavior and could make native and JNI splits disagree. Paimon nested filter-only TIMESTAMP_LTZ columns could also lose their table-format timestamp annotation while building the file projection. In addition, a fuzzy session variable could disable COUNT pushdown for a multi-gigabyte MAP regression fixture and cause scanner v2 to materialize the payload under ASAN.
Keep Hudi native and JNI timestamp decoding on the SQL session timezone, propagate Paimon timestamp semantics into filter-only projections, and cover the precision-9 INT96 path. Make COUNT pushdown deterministic only for the large MAP fixture so scanner v2 reads definition levels while scanner v1 retains its existing behavior.
Copy file name to clipboardExpand all lines: fe/be-java-extensions/hadoop-hudi-scanner/src/test/java/org/apache/doris/hudi/HadoopHudiColumnValueTest.java
0 commit comments