[SPARK-33533][SQL] Fix the regression bug that ConnectionProviders don't consider case-sensitivity for properties. #30485
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.
What changes were proposed in this pull request?
This PR fixes an issue that
BasicConnectionProviderdoesn't consider case-sensitivity for properties.For example, the property
oracle.jdbc.mapDateToTimestampshould be considered case-sensitivity but it is not considered.Why are the changes needed?
This is a bug introduced by #29024 .
Caused by this issue,
OracleIntegrationSuitedoesn't pass.Does this PR introduce any user-facing change?
No.
How was this patch tested?
With this change, I confirmed that
OracleIntegrationSuitepasses with the following command.