Support workarounds for the presence of Readers with different instance types (Amazon Aurora) - Githubissues

aws / aws-advanced-jdbc-wrapper

The Amazon Web Services JDBC Driver has been redesigned as an advanced JDBC wrapper. This wrapper is complementary to and extends the functionality of an existing JDBC driver to help an application take advantage of the features of clustered databases such as Amazon Aurora.

Apache License 2.0

195 stars 37 forks source link

Support workarounds for the presence of Readers with different instance types (Amazon Aurora) #949

Open dekachiri opened 4 months ago

dekachiri commented 4 months ago

Describe the feature

Support for custom endpoints or the ability to enumerate only the instance endpoints you want to use, as in previous versions of MariaDB Connector/J.

Use Case

If you do not want to use db-instance-4 for user access in the following clusters, the aws-advanced-jdbc-wrapper is not available.

db-instance-1: 4xlarge, writer
db-instance-2: 4xlarge, reader
db-instance-3: 4xlarge, reader
db-instance-4: large, reader

db-instance-4 is used for analysis and batch applications and has insufficient resources for user access.

Proposed Solution

At the moment I can't think of a good implementation method.

Other Information

No response

Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

The AWS Advanced JDBC Driver version used

2.3.5

JDK version used

Corretto-17.0.10.7.1

Operating System and version

Amazon Linux 2023

aaronchung-bitquill commented 3 months ago

Hi @dekachiri

We can confirm that Custom Endpoint Support is a feature that is currently in our backlog and that we'll share feedback to the team for prioritization. We'll keep this ticket updated with any movement.

Thank you!