deps: update opentelemetry.version to v1.45.0 by renovate-bot · Pull Request #3531 · googleapis/java-spanner (original) (raw)

This PR allows users to set the custom monitoring host for built in metrics.

This PR introduces java.time alternatives to existing org.threeten.bp.* methods, as well as switching internal variables (if any) to java.time

The main constraint is to keep the changes backwards compatible, so for each existing threeten method "method1(org.threeten.bp.Duration)" we will add an alternative with a Duration (or Timestamp when applicable) suffix: "method1Duration(java.time.Duration)".

For most cases, the implementation will be held in the java.time method and the old threeten method will just delegate the call to it. However, for the case of abstract classes, the implementation will be kept in the threeten method to avoid breaking changes (i.e. users that already overloaded the method in their user code).

Co-authored-by: Knut Olav Løite koloite@gmail.com

Co-authored-by: Knut Olav Løite koloite@gmail.com


Co-authored-by: Knut Olav Løite koloite@gmail.com

Multiple tests were skipped on the Emulator, because the features that are covered by these tests were originally not supported on the Emulator. These features are now available on the Emulator, and the tests can be enabled.

The Connection API by default uses either a platform thread or a virtual thread for each connection to execute and control the statements of that connection. This is used to enable asynchronous execution of statements and allows a statement to be cancelled by just interrupting this thread. Both these use cases are however not (or only very rarely) used by the most common users of the Connection API; the JDBC driver and PGAdapter. PGAdapter uses the PostgreSQL wire-protocol, which by design is synchronous, and JDBC is also a synchronous API. The latter has a cancel() method that currently requires this threading model, but this can be modified in the JDBC driver.

Using a direct executor instead of a single-threaded executor per connection can save one thread per connection.

The option is intentionally made package-private, so the above-mentioned frameworks can set it by default without it becoming part of the public API.

Adds support for set local retry_aborts_internally=true|false in the Connection API. This change also adds the parsing infrastructure that is needed to support set local for all connection variables. Support for this will be added to other connection variables in follow-up pull requests.


Co-authored-by: cloud-java-bot cloud-java-bot@google.com

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

Reset the default to using a platform thread for connections. This was the default before adding an option for setting the executor type, and the new default is causing problems with the async Connection API.

Fixes #3541


Co-authored-by: rahul2393 irahul@google.com Co-authored-by: Joe Wang joewa@google.com


Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: cloud-java-bot cloud-java-bot@google.com

Mark the state field in AsyncResultSetImpl volatile, as it is inspected by different threads.


Co-authored-by: rahul2393 irahul@google.com

Make the list of valid connection properties public, so tools that depend on the Connection API can use this to for example generate documentation for valid properties.

Also add valid values to the connection properties that have that (e.g. enums and booleans).

Co-authored-by: rahul2393 irahul@google.com

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.opentelemetry:opentelemetry-sdk-testing 1.44.1 -> 1.45.0 age](https://docs.renovatebot.com/merge-confidence/) adoption](https://docs.renovatebot.com/merge-confidence/) passing](https://docs.renovatebot.com/merge-confidence/) confidence](https://docs.renovatebot.com/merge-confidence/)
io.opentelemetry:opentelemetry-sdk-trace 1.44.1 -> 1.45.0 age](https://docs.renovatebot.com/merge-confidence/) adoption](https://docs.renovatebot.com/merge-confidence/) passing](https://docs.renovatebot.com/merge-confidence/) confidence](https://docs.renovatebot.com/merge-confidence/)
io.opentelemetry:opentelemetry-sdk-metrics 1.44.1 -> 1.45.0 age](https://docs.renovatebot.com/merge-confidence/) adoption](https://docs.renovatebot.com/merge-confidence/) passing](https://docs.renovatebot.com/merge-confidence/) confidence](https://docs.renovatebot.com/merge-confidence/)
io.opentelemetry:opentelemetry-sdk 1.44.1 -> 1.45.0 age](https://docs.renovatebot.com/merge-confidence/) adoption](https://docs.renovatebot.com/merge-confidence/) passing](https://docs.renovatebot.com/merge-confidence/) confidence](https://docs.renovatebot.com/merge-confidence/)

Release Notes

open-telemetry/opentelemetry-java (io.opentelemetry:opentelemetry-sdk-testing)

v1.45.0

Compare Source

API
SDK
Traces
Metrics
Logs
Exporters
Extensions
Tooling

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.



This PR was generated by Mend Renovate. View the repository job log.

🤖 I have created a release beep boop

Updating meta-information for bleeding-edge SNAPSHOT release.


This PR was generated with Release Please. See documentation.

Co-authored-by: rahul2393 irahul@google.com

Spanner occasionally returns INTERNAL errors regarding the auth backend server. These errors should be regarded as retryable.

Some specific internal errors should be retrid. Instead of adding INTERNAL as a standard retryable error code, we use an interceptor to catch and translate those specific errors.

See also b/375684610

Native metrics were automatically disabled when the emulator is used, but some clients (e.g. PGAdapter) set up the connection to the emulator manually instead of setting the environment variable. Also, when using in-mem mock servers, native metrics should be disabled, as they cannot be exported.

This PR therefore adds an additional check that disables native metrics when the client uses a NoCredentials instance.

There are SPANNER_SYS tables that contain ARRAY columns. Adding support for this in the CloudClientExecutor so that queries involving these tables do not throw an error.


Co-authored-by: surbhigarg92 surbhigarg.92@gmail.com Co-authored-by: Diego Marquez diegomarquezp@google.com Co-authored-by: Sri Harsha CH 57220027+harshachinta@users.noreply.github.com Co-authored-by: Knut Olav Løite koloite@gmail.com Co-authored-by: Pratick Chokhani pratick@google.com Co-authored-by: Sakthivel Subramanian 179120858+sakthivelmanii@users.noreply.github.com Co-authored-by: cloud-java-bot cloud-java-bot@google.com Co-authored-by: Pratick Chokhani pratick.chokhani@gmail.com Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Mend Renovate bot@renovateapp.com Co-authored-by: cloud-java-bot 122572305+cloud-java-bot@users.noreply.github.com Co-authored-by: rahul2393 irahul@google.com Co-authored-by: Joe Wang joewa@google.com Co-authored-by: Sagnik Ghosh sagnikghosh@google.com Co-authored-by: larkee 31196561+larkee@users.noreply.github.com Co-authored-by: Gagan Gupta guptagg@google.com