Handle Oracle NUMBER correctly by letting JdbcArrowTypeConverter hand… #2573
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oracle NUMBER with no precision or scale specified allows for Oracle users to have a dynamic number of decimal points. This means NUMBER column can have the value 10.123123 for one entry and 10 for the other entry.
This is not reflected properly in our connector. This fix removes the
precision == 0
check (originally, mis-wrote asscale == 0
) on line 381 because JdbcArrowTypeConverter.java handles that on line 51. Seeaws-athena-query-federation/athena-jdbc/src/main/java/com/amazonaws/athena/connectors/jdbc/manager/JdbcArrowTypeConverter.java
Line 51 in 3afa6ab
With above change, customers can now specify
default_scale
in lambda environment variables to capture the Oracle NUMBER's decimal points.It also changes line 381 to include 0 to correctly convert 0 scale DECIMAL to arrow BIGINT.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.