hudi
hudi copied to clipboard
apache
[HUDI-9424]Support using local timezone when writing flink TIMESTAMP data
Change Logs
This PR makes the changes to support using local timezone when writing flink TIMESTAMP data.
Impact
User can use utc or local timezone to write flink TIMESTAMP date.
Risk level (write none, low medium or high below)
low
Documentation Update
Add new flink config option "write.utc-timezone". Default value is "true" for forward compatibility.
Contributor's checklist
- [x] Read through contributor's guide
- [x] Change Logs and Impact were stated clearly
- [x] Adequate tests were added if applicable
- [ ] CI passed
Related items https://github.com/apache/hudi/pull/7886 , https://github.com/apache/hudi/pull/7904
The travis tests still got falures.
I find Timezone in JVM Properties is used to convert Flink TimestampData to Timestamp. This is the reason that IT succeeded locally and failed in CI. So I add code to set timezone in order to ensure that IT runs in the same environment.
There are still test failures: https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=22545&view=logs&j=600e7de6-e133-5e69-e615-50ee129b3c08&t=bbbd7bcc-ae73-56b8-887a-cd2d6deaafc7
There are still test failures: https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=22545&view=logs&j=600e7de6-e133-5e69-e615-50ee129b3c08&t=bbbd7bcc-ae73-56b8-887a-cd2d6deaafc7
Is there any way to rerun failed unit test? The failed unit test succeeded locally and I think the code change is not related with failed unit test. Failed test is a unit test in hudi-spark-client module.
