-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[hotfix][maxcompute] Fix MaxCompute Pipeline Connector unit tests by upgrading maxcompute-emulator #3862
Conversation
Could @leonardBang trigger the CI workflow please? |
Seems there's still some timezone related test failures...
Could @dingxin-tech please redesign the test case to make it time-zone unaware, and could run with any time-zone configuration? (We may run tests in randomized timezones in the future like #3650.) |
done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -167,7 +167,7 @@ public void testRecordConvert() { | |||
123456.789d, | |||
12345, | |||
12345, | |||
TimestampData.fromTimestamp(Timestamp.from(Instant.ofEpochSecond(0))), | |||
TimestampData.fromTimestamp(Timestamp.valueOf("1970-01-01 00:00:00")), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor: TimestampData.fromLocalDateTime
is recommended
This PR fixes failing unit tests in MaxCompute Pipeline Connector by upgrading the maxcompute-emulator dependency from 0.0.4 to 0.0.7.
Changes
maxcompute-emulator
version in org.apache.flink.cdc.connectors.maxcompute.EmulatorTestBase