Repository navigation
JDBC sources: Fix unexcepcted long Integer value failure - #3846
Conversation
…o cover the case with too large value (possible for some sources)
Sherif A. Nada (sherifnada)
left a comment
There was a problem hiding this comment.
LGTM -- please publish and merge. Also, can you add this to the data type tests?
BTW see the definition-of-done checklist here to help clarify what next steps would be: #3864
|
Andrii Leonets (@DoNotPanicUA) also can you update the PR title to match best practices for PR titles? |
|
/test connector=source-mysql
|
|
/test connector=source-jdbc
|
|
/test connector=source-mssql
|
|
/test connector=source-oracle
|
|
/test connector=source-postgres
|
|
/test connector=source-redshift
|
|
/test connector=source-clickhouse
|
|
/test connector=destination-snowflake
|
|
/test connector=destination-jdbc
|
|
/test connector=destination-mysql
|
|
/test connector=destination-mssql
|
|
/test connector=destination-postgres
|
|
/test connector=destination-redshift
|
|
/test connector=destination-snowflake
|
This case is added to the PR with tests. Corresponding commit. |
|
/publish connector=connectors/source-mysql
|
Issue: #3840
What
Fix an error when JDBC source produces Integer value bigger than max Java Integer value.
How
Implement handler which tries to convert into Integer first. My assumption is that at most cases the value will be in the range.
If it fails, the handler tries to convert into the Long type. In all other negative cases it will replace value by
null.Pre-merge Checklist
Recommended reading order
JdbcUtils.java