--- title: Debezium 3.7.0.Alpha1 Released | daily.dev description: Debezium 3.7.0.Alpha1 is the first preview release of the 3.7 series, resolving 97 issues and introducing a wide range of new features. Highlights include... canonical: https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Debezium 3.7.0.Alpha1 Released | daily.dev og:description: Debezium 3.7.0.Alpha1 is the first preview release of the 3.7 series, resolving 97 issues and introducing a wide range of new features. Highlights include... og:url: https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj og:image: https://api.daily.dev/og/posts/61rTnGMjj.png og:image:alt: Debezium 3.7.0.Alpha1 Released og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Debezium 3.7.0.Alpha1 Released **[Debezium](https://daily.dev/sources/debezium)** · 18 min read · 3 upvotes · 0 comments ## Summary Debezium 3.7.0.Alpha1 is the first preview release of the 3.7 series, resolving 97 issues and introducing a wide range of new features. Highlights include incubating connectors for Ingres and YashanDB, a new ExtendedTimestamp type to handle high-precision timestamps beyond INT64 limits, and expanded JDBC sink support with CockroachDB, SingleStore, and Starrocks dialects. Core improvements cover schema history memory deduplication for multi-tenant deployments, LOB re-selection caching to reduce source database load, and configurable shutdown strategies for the embedded engine. The Oracle connector gains downstream mining support for both XStream and LogMiner, while PostgreSQL gets first-class geometric type mapping. The CockroachDB connector adds sinkless changefeed support, eliminating the need for an intermediate Kafka cluster. PyDebeziumAI now supports PGVector and Milvus backends alongside Chroma for CDC-to-vector synchronization. Platform and operator improvements include reduced OTel metrics latency, JMX metrics for the JDBC sink, and new CLI commands for connection, transform, and pipeline log management. Breaking changes affect MySQL-to-MySQL JDBC sink pipelines due to type preservation fixes. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What breaking changes should I check before upgrading to Debezium 3.7.0.Alpha1's MySQL JDBC sink? Several MySQL data types previously silently corrupted or mishandled in MySQL-to-MySQL JDBC sink pipelines are now fixed, so behaviors that appeared to work before but produced wrong data may now surface as errors. Affected types include BIGINT UNSIGNED max values, BIT(>1) columns with Avro converters, ENUM/SET values with commas or quotes, spatial coordinate ordering, and TIME values outside the standard clock range. _Track breaking JDBC sink changes like these on daily.dev before rolling out a Debezium upgrade._ ### How does the ExtendedTimestamp type in Debezium 3.7 avoid overflow for high-precision timestamps? The io.debezium.time.ExtendedTimestamp semantic type separates calendar range from sub-second precision using a composite STRUCT with seconds and nanos fields, avoiding the silent overflow that affected MicroTimestamp and NanoTimestamp at the boundaries of INT64 representable ranges. This mirrors the design used by Java's Instant and Google Protocol Buffers Timestamp, targeting databases like PostgreSQL, Oracle, and SQL Server that support wider timestamp ranges than INT64 can hold. _Developers modeling far-future or high-precision timestamps can follow CDC updates like this via daily.dev._ ### Does Debezium's JDBC sink support writing to CockroachDB and SingleStore? Yes, Debezium 3.7.0.Alpha1 adds a dedicated CockroachDB dialect that generates proper INSERT ... ON CONFLICT ... DO UPDATE upsert statements instead of falling back to a generic PostgreSQL workaround, and a new SingleStore dialect handles that database's MySQL-wire-protocol-compatible but syntactically distinct SQL, though geospatial type support for SingleStore is planned for a future release. _Evaluating JDBC sink targets for a CDC pipeline is easier when tracking dialect support changes on daily.dev._ ## Similar posts on daily.dev - [Debezium 3.7 Release Summary](https://daily.dev/posts/debezium-3-7-release-summary-mdx3ounvr) · Debezium · 4 upvotes · 0 comments - [Debezium 3.7.0.Alpha2 Released](https://daily.dev/posts/debezium-3-7-0-alpha2-released-9p8szrw3k) · Debezium · 2 upvotes · 0 comments - [Debezium 3.7.0.Beta1 Released](https://daily.dev/posts/debezium-3-7-0-beta1-released-r3h2ycqun) · Debezium · 5 upvotes · 1 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#postgresql](https://daily.dev/tags/postgresql), [#apache-kafka](https://daily.dev/tags/apache-kafka), [#change-data-capture](https://daily.dev/tags/change-data-capture), [#debezium](https://daily.dev/tags/debezium) [View this post on daily.dev](https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Debezium 3.7.0.Alpha1 Released","url":"https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj"},"datePublished":"2026-07-31T09:42:19.682Z","dateModified":"2026-09-14T08:48:21.519Z","description":"Debezium 3.7.0.Alpha1 is the first preview release of the 3.7 series, resolving 97 issues and introducing a wide range of new features. Highlights include...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b489c09207779f155dbc5881f8b50feb?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b489c09207779f155dbc5881f8b50feb?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Debezium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Debezium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/ee970fdcd78942b68304416ca68d7d1a","url":"https://daily.dev/sources/debezium"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,postgresql,apache-kafka,change-data-capture,debezium","timeRequired":"PT18M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Debezium","item":"https://daily.dev/sources/debezium"},{"@type":"ListItem","position":3,"name":"Debezium 3.7.0.Alpha1 Released"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/debezium-3-7-0-alpha1-released-61rtngmjj#faq","mainEntity":[{"@type":"Question","name":"What breaking changes should I check before upgrading to Debezium 3.7.0.Alpha1's MySQL JDBC sink?","acceptedAnswer":{"@type":"Answer","text":"Several MySQL data types previously silently corrupted or mishandled in MySQL-to-MySQL JDBC sink pipelines are now fixed, so behaviors that appeared to work before but produced wrong data may now surface as errors. Affected types include BIGINT UNSIGNED max values, BIT(>1) columns with Avro converters, ENUM/SET values with commas or quotes, spatial coordinate ordering, and TIME values outside the standard clock range. Track breaking JDBC sink changes like these on daily.dev before rolling out a Debezium upgrade."}},{"@type":"Question","name":"How does the ExtendedTimestamp type in Debezium 3.7 avoid overflow for high-precision timestamps?","acceptedAnswer":{"@type":"Answer","text":"The io.debezium.time.ExtendedTimestamp semantic type separates calendar range from sub-second precision using a composite STRUCT with seconds and nanos fields, avoiding the silent overflow that affected MicroTimestamp and NanoTimestamp at the boundaries of INT64 representable ranges. This mirrors the design used by Java's Instant and Google Protocol Buffers Timestamp, targeting databases like PostgreSQL, Oracle, and SQL Server that support wider timestamp ranges than INT64 can hold. Developers modeling far-future or high-precision timestamps can follow CDC updates like this via daily.dev."}},{"@type":"Question","name":"Does Debezium's JDBC sink support writing to CockroachDB and SingleStore?","acceptedAnswer":{"@type":"Answer","text":"Yes, Debezium 3.7.0.Alpha1 adds a dedicated CockroachDB dialect that generates proper INSERT ... ON CONFLICT ... DO UPDATE upsert statements instead of falling back to a generic PostgreSQL workaround, and a new SingleStore dialect handles that database's MySQL-wire-protocol-compatible but syntactically distinct SQL, though geospatial type support for SingleStore is planned for a future release. Evaluating JDBC sink targets for a CDC pipeline is easier when tracking dialect support changes on daily.dev."}}]} ```