Skip to content

[DBZ-8299] feat: upgrade quarkus#5929

Closed
varsis wants to merge 98 commits intodebezium:mainfrom
varsis:DBZ-8299
Closed

[DBZ-8299] feat: upgrade quarkus#5929
varsis wants to merge 98 commits intodebezium:mainfrom
varsis:DBZ-8299

Conversation

@varsis
Copy link

@varsis varsis commented Oct 9, 2024

This PR upgrades Quarkus and OpenTelemetry to allow compatibility with Java PubSub OpenTelemetry supported version.

See related PR: debezium/debezium-server#130 (WIP at this moment)

@github-actions
Copy link

github-actions bot commented Oct 9, 2024

Hi @varsis, thanks for your contribution. Please prefix the commit message(s) with the DBZ-xxx JIRA issue key.

chore: add back comment
pom.xml Outdated
<!-- Quarkus -->
<!-- Version used for Outbox extension development, changes frequently to align with latest Quarkus -->
<quarkus.version.extension>3.14.0</quarkus.version.extension>
<quarkus.version.extension>3.15.1</quarkus.version.extension>
Copy link
Member

Choose a reason for hiding this comment

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

Hi, I just bumped the Outbox to 3.16.3 in #5993. I'd prefer we not change that in this PR and instead focus on the OTEL and Quarkus runtime version only to 3.15.1, to focus this commit on DS, operator, and non-extension bits.

Copy link
Author

Choose a reason for hiding this comment

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

@Naros Updated

obabec and others added 25 commits November 17, 2024 14:17
…a/io/debezium/testing/system/tools/kafka/connectors/RestPrometheusMetricReader.java

Co-authored-by: Jiri Pechanec <[email protected]>
When GTID is enabled, binlog client tracks GTID and eventually resumes
from the last GTID position. However, to enable GTID on the client,
client has to set initial GTID position (can be empty). When GTID is
enbled in the connector, always enable GTID also on the binlog client
to make sure that it tracks GTID and its keep alive thread eventually
resumes from the right position.
Currently Debezium server allows to use only sinks which implements
`ChangeConsumer` interface, which excludes these options. Listing
these properties may be confusing for users. Remove them until we
actually allow to use them in the Debezium sever.
twthorn and others added 27 commits November 17, 2024 14:17
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 45.0.3 to 45.0.4.
- [Release notes](https://github.com/tj-actions/changed-files/releases)
- [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md)
- [Commits](tj-actions/changed-files@v45.0.3...v45.0.4)

---
updated-dependencies:
- dependency-name: tj-actions/changed-files
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
As we may miss one record (the last one, see DBZ-8335) when Debezium
hit some error while running blocking snapshot and records don't have
to be ordered by the primary key, we may be missing any record, not only
the record with highest PK.
Modify snapshot query to always return ordered records, so the
eventually missed records is the last one.
… inside Debezium sink connectors

- pt.1 Refactor TableId to CollectionId and related classes/variable name changes and refactoring, introduce debezium-sink package
… inside Debezium sink connectors

- pt.2 Switching to DebeziumSinkRecord instead of SinkRecord
… inside Debezium sink connectors

- pt.3 Add Field#withDeprecatedAliases for backward compatible aliases for config options
- updated documentation
… inside Debezium sink connectors

- pt.4 Re-Add deprecated implementations to not harm existing user implementations using the old API / config options (DefaultTableNamingStrategy, TableNamingStrategy), incl test scenarios
…sitivity (debezium#5991)

* DBZ-8358 Improve blocking snapshot signal description around case sensitivity

---------

Co-authored-by: roldanbob <[email protected]>
Co-authored-by: Chris Cranford <[email protected]>
chore: add back comment
@ismailsimsek
Copy link
Contributor

@Naros what is the plan with Quarkus upgrade? is it planned for Debezium 3.1?

@Naros
Copy link
Member

Naros commented Jan 23, 2025

Hi @ismailsimsek, yes I would like to move Debezium 3.0 and later to Quarkus 3.15.x for Debezium Server.

@varsis varsis closed this Jul 8, 2025
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.