Skip to content

Conversation

@Naros
Copy link
Member

@Naros Naros commented Dec 2, 2025

@jpechane I opted to exclude the items that were in italics, as those IIRC were items that we said were tentative. Should I include those here or not?

Signed-off-by: Chris Cranford <[email protected]>
@github-actions
Copy link

github-actions bot commented Dec 2, 2025

🎊 PR Preview has been successfully built and deployed to https://debezium-debezium-github-io-preview-pr-1199.surge.sh

@jpechane
Copy link
Contributor

jpechane commented Dec 3, 2025

@jpechane I opted to exclude the items that were in italics, as those IIRC were items that we said were tentative. Should I include those here or not?

@Naros It is not necessary, there is no capacity for us to work on it anyway

@mfvitale
Copy link
Member

mfvitale commented Dec 3, 2025

@jpechane

* Debezium component descriptors / registry - Q1/half Q2
* Provide easy access to Debezium documentation - Q1 
* Offset manipulation - Q2
	* Backend start supporting JDBC offset storage since it is the default
	* UX/UI POC
* Trigger schema refresh to easily add new table to include list - Q2
* Notification - Q3
	* Send notification about K8s events for DebeziumServer CRD
	* Progress of incremental snapshot 
* Revisit transforms to be not shared and provide a template mechanisms to share common settings.  - Q3
	* UX/UI to manage the concept of template - Q1
* Vaults support - Q4

This was the initial proposal for the Platform and IIRC then we had a discussion to to remove "Offset manipulation" and "Trigger schema refresh to easily add new table to include list " from Q2 adding Monitor and alerting and then add IAM to Q4? So "Offset manipulation" and "Trigger schema refresh to easily add new table to include list " and "Vaults support" will be for next year

Anything changed in this regards?

roadmap.asciidoc Outdated
* [Core] Remove dependency on Kafka Connect APIs
* [Debezium Server] CLI support
* [Quarkus Extension] CLI support
* [Platform] Component descriptors/registry
Copy link
Member

Choose a reason for hiding this comment

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

This will be mainly in Q1 and eventually will continue in half Q2

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll put it in Q1, and if it slips or there are portions left for Q2, we can bump the specifics in the roadmap just before Q2 to provide more context if needed. Does that work for you?

roadmap.asciidoc Outdated
* Create PoC for implementing sagas (long-running business transactions spanning multiple (micro-)services) using CDC and the outbox pattern
* Explore and provide building blocks for implementing CQRS architectures based on change data streams
* Add schema history compaction tool
* Debezium UI (Legacy) - New CLI tooling
Copy link
Member

Choose a reason for hiding this comment

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

Haven't we archived the repo? Those this still make sense?

Copy link
Member Author

Choose a reason for hiding this comment

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

Ya I think that was just left over from what was there previously, great catch. I removed it.

@mfvitale
Copy link
Member

mfvitale commented Dec 3, 2025

@jpechane @Naros Could we add in the Future releases section

  1. Debezium Server Fluss sink
  2. DEbezium Server WASM sink

WDYT?

@Naros
Copy link
Member Author

Naros commented Dec 4, 2025

@mfvitale regarding #1199 (comment), I'll wait and amend once Jiri chimes in. It's very likely that was just not documented well somewhere and it was just missed.

Copy link
Member

@vjuranek vjuranek left a comment

Choose a reason for hiding this comment

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

From my point of view LGTM.

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.

5 participants