rangareddy commented on issue #17365: URL: https://github.com/apache/hudi/issues/17365#issuecomment-4892569201
This issue was reviewed as part of the JIRA-migrated backlog triage and reproduced/validated on the spark-hudi container (Spark 3.4). Findings: the timestamp-based partitioning defect reproduces on 0.15.0 and is fixed on current Hudi. Test: CustomKeyGenerator with partitionpath.field=ts:timestamp,segment:simple (SCALAR seconds, yyyyMM). - On 0.15.0, reading back returns the partition-derived value in the ts column (ts=[202312,202401,202402]) instead of the original epochs - the reported 'field replaced with partition value' bug. - On 1.2.0 the ts column returns the original epochs [1701443427,1704121827,1706800227] - fixed. (delete_partition worked correctly on both in a single-partition-drop check.) The fix was targeted at 0.15.1, which was never released (0.15.x is EOL - releases go 0.15.0 -> 1.0.0 -> 1.2.0), and 1.0+ already works, so no supported version still exhibits this and there is no backport target. Closing as fixed on supported versions. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
