-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
fix temporal data type handling in mysql source #15504
Conversation
…x-temporal-type-handling-mysql
…x-temporal-type-handling-mysql
/test connector=connectors/source-mysql
Build FailedTest summary info:
|
# Conflicts: # airbyte-db/db-lib/src/main/java/io/airbyte/db/jdbc/DateTimeConverter.java
/test connector=connectors/source-mysql |
/test connector=connectors/source-mysql
Build FailedTest summary info:
|
/test connector=connectors/source-mysql |
/test connector=connectors/source-mysql
Build PassedTest summary info:
|
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.
yep, it covers all the data types for that issue (date/datetime/timestamp)
added a few comments, but nothing relevant to the actual code change
try { | ||
preparedStatement.setObject(parameterIndex, LocalDateTime.parse(value)); | ||
} catch (final DateTimeParseException e) { | ||
// attempt to parse the datetime with timezone. This can be caused by schema created with an older |
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.
are there test cases for this behavior?
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.
added tests for the behaviour
.sourceType("timestamp") | ||
.airbyteType(JsonSchemaType.STRING_TIMESTAMP_WITH_TIMEZONE) | ||
.addInsertValues("null", "'2021-01-00'", "'2021-00-00'", "'0000-00-00'", "'2022-08-09T10:17:16.161342Z'") | ||
.addExpectedValues(null, null, null, null, "2022-08-09T10:17:16.000000Z") |
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.
why are these returning null? is it because the insert values aren't valid timestamps?
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.
Yup
container.start(); | ||
|
||
config = Jsons.jsonNode(ImmutableMap.builder() | ||
.put(JdbcUtils.HOST_KEY, container.getHost()) |
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.
prefer HostPortResolver.resolveHost() and resolvePort() for the host/portname - otherwise this breaks on m1 macs (maybe? at the very least, george and I had issues with postgres tests which were fixed by switching to HostPortResolver)
(iirc the DSLContextFactory still needs to use container.getHost/getPort because that's running directly on the host laptop, not inside a container)
.sourceType("timestamp") | ||
.airbyteType(JsonSchemaType.STRING_TIMESTAMP_WITH_TIMEZONE) | ||
.addInsertValues("null", "'2021-01-00'", "'2021-00-00'", "'0000-00-00'", "'2022-08-09T10:17:16.161342Z'") | ||
.addExpectedValues(null, "1970-01-01T00:00:00.000000Z", "1970-01-01T00:00:00.000000Z", "1970-01-01T00:00:00.000000Z", |
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.
is 1970-01-01 the equivalent of the null
entries in the default test cases? (adding this as a comment would be helpful)
/test connector=connectors/source-mysql
Build FailedTest summary info:
|
/test connector=connectors/source-mysql
Build PassedTest summary info:
|
Issue : #14628, #15381
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changesTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.