Case resolver jdbc #2655
Merged
Case resolver jdbc #2655
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #2655 +/- ##
============================================
+ Coverage 60.68% 60.88% +0.20%
- Complexity 3871 3897 +26
============================================
Files 593 602 +9
Lines 22130 21991 -139
Branches 2732 2707 -25
============================================
- Hits 13430 13390 -40
+ Misses 7398 7288 -110
- Partials 1302 1313 +11 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
chngpe
force-pushed
the
case_resolver_jdbc
branch
2 times, most recently
from
d9df3ef to
ac0155f
Compare
aimethed
reviewed
Mar 20, 2025
...ederation-sdk/src/main/java/com/amazonaws/athena/connector/lambda/resolver/CaseResolver.java
Outdated
Show resolved
Hide resolved
...ain/java/com/amazonaws/athena/connectors/postgresql/resolver/PostGreSqlJDBCCaseResolver.java
Show resolved
Hide resolved
...rc/main/java/com/amazonaws/athena/connectors/redshift/resolver/RedshiftJDBCCaseResolver.java
Show resolved
Hide resolved
… to expand search capabilities only need to provide information schema query -Clean up duplication code. -Introduce case resolver to FederationSDK -Introduce Default JDBC case resolver for JDBC connectors. If we want to expand search capabilities only need to provide information schema query -Clean up duplication code. -Fix pagination token, return null when empty or last records. Standardize Case resolver support for below JDBC connectors: 1. DataLakeGen2 2. Snowflake 3. Oracle 4. Synapse 5. SapHana 6. MySQL 7. PostGreSql 9. ClickHouse uncomment pom
… mixed cased fix checkstyle
…per case object with casing_mode = CASE_SENSITIVE_SEARCH
chngpe
force-pushed
the
case_resolver_jdbc
branch
from
01d42a0 to
ef1e148
Compare
chngpe
force-pushed
the
case_resolver_jdbc
branch
from
ef1e148 to
64f94c2
Compare
aimethed
approved these changes
Mar 31, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Apr 8, 2025
- Error handling changes for Elasticsearch connector (#2279) - build(deps): bump aws-sdk-v2.version from 2.31.14 to 2.31.16 (#2709) - build(deps): bump net.snowflake:snowflake-jdbc from 3.23.1 to 3.23.2 (#2710) - build(deps-dev): bump nl.jqno.equalsverifier:equalsverifier from 3.19.2 to 3.19.3 (#2712) - build(deps): bump net.sf.jt400:jt400 from 21.0.0 to 21.0.3 (#2711) - build(deps): bump software.amazon.awssdk:cloudwatchlogs from 2.31.14 to 2.31.16 (#2708) - build(deps): bump com.sap.cloud.db.jdbc:ngdbc from 2.24.6 to 2.24.7 (#2707) - build(deps): bump software.amazon.awssdk:cloudwatchlogs from 2.31.11 to 2.31.14 (#2704) - build(deps): bump org.jacoco:jacoco-maven-plugin from 0.8.12 to 0.8.13 (#2703) - build(deps): bump com.zaxxer:HikariCP from 6.2.1 to 6.3.0 (#2706) - build(deps): bump software.amazon.jsii:jsii-runtime from 1.110.0 to 1.111.0 (#2705) - build(deps): bump aws-sdk-v2.version from 2.31.11 to 2.31.14 (#2702) - Explicitly ignore dependency updates in validation_testing (#2701) - Revert "build(deps): bump aws-cdk-lib from 2.177.0 to 2.186.0 in /val… (#2700) - Updated rds truststore to default truststore for oracle and docdb. (#2698) - build(deps): bump aws-cdk-lib from 2.177.0 to 2.186.0 in /validation_testing/cdk_federation_infra_provisioning/app (#2697) - Case resolver jdbc (#2655) - build(deps): bump org.elasticsearch.client:elasticsearch-rest-client from 8.17.3 to 8.17.4 (#2695) - build(deps): bump surefire.failsafe.version from 3.5.2 to 3.5.3 (#2693) - build(deps): bump software.amazon.awssdk:cloudwatchlogs from 2.31.6 to 2.31.11 (#2696) - build(deps): bump org.junit.support:testng-engine from 1.0.5 to 1.0.6 (#2692) - build(deps): bump aws-sdk-v2.version from 2.31.6 to 2.31.11 (#2691)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.