Skip to content

Conversation

@karenc-bq
Copy link
Contributor

Summary

Description

Before establishing connections using the DataSource, the wrapper removes all wrapper-specific connection properties to avoid errors. This can be problematic when the connection fails and the wrapper needs to access wrapper-specific properties to perform specific handling. This fix moves the removal logic to the lowest-level method possible to address this issue.

Additional Reviewers

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

…orrectly accessed after removing wrapper specific properties before connecting
@github-actions
Copy link

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true
Contact Qodana team

Contact us at [email protected]

Copy link

@leszek-bq leszek-bq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@karenc-bq karenc-bq merged commit cf4420e into main Jul 19, 2024
@karenc-bq karenc-bq deleted the fix/enable-green-node-replacement branch June 13, 2025 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

enableGreenNodeReplacement doesn't work for Aurora MySQL

2 participants