June 2026 monthly summary for debezium/debezium: Key feature delivered: - TIMESTAMP Column Mapping Enhancement for Kafka Connect Compatibility: Implemented a new mapping for TIMESTAMP columns driven by time.precision.mode, enabling Kafka Connect's Timestamp logical type for MySQL TIMESTAMP when using the Vitess connector. This aligns Debezium's timestamp semantics with Connect expectations and reduces downstream transformation needs. - Commit reference: b332125656f9bf68d3ed75b1e0b6424de1aae1eb; message highlights documenting TIMESTAMP mapping for time.precision.mode=connect and honoring connect semantics in Vitess connector. - Action taken: Added TIMESTAMP row to the connect-mode mapping table and scoped temporal-types introduction accordingly. Major bugs fixed: - No reportable critical bugs fixed this month for this repository; the focus was on feature enhancement and alignment with Kafka Connect semantics to reduce data-type drift in pipelines. Overall impact and accomplishments: - Improved cross-system data consistency and interoperability for streaming workloads that rely on Debezium, Vitess, and Kafka Connect. Customers benefit from correct TIMESTAMP typing in Connect pipelines, fewer downstream data type conversions, and more predictable analytics. - Documentation and mapping changes were completed in tandem with the feature, supporting faster adoption and reduced onboarding efforts for teams integrating Vitess with Kafka Connect. Technologies/skills demonstrated: - Kafka Connect logical types and TIMESTAMP handling, time.precision.mode, and Debezium/ Vitess integration patterns. - Careful mapping table updates and inline documentation to enable future temporal-type extensions. - Clear, production-ready commit messaging and codebase contribution workflow.