Debezium Connector启动,但无法从CDC返回表

发布于 2025-02-05 20:09:10 字数 3169 浏览 2 评论 0原文

我正在使用SQL Server连接器,日志显示锁定捕获的表[] - 未捕获表。我已经验证了模式,表格和数据库。我已经尝试了以下所有内容,所有这些主题已预先创建

  • 。 “ schema.include.list”:“ dbo”
  • “ table.include.list”:“ dbo.testtable”&&& “ schema.include.list”:“ dbo”
  • “ table.include.list”:“ dbname.dbo.testtable”&& “ schema.include.list”:“ dbo”
  • “ table.include.list”:“ dbname.dbo.testtable”
  • “ table.include.list”:“ dbo.testtable”

的想法,没有捕获数据。 。

2022-06-09T01:28:35.036573+00:00 app[web.1]: [2022-06-09 01:28:35,036] INFO Snapshot step 3 - Locking captured tables [] (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.036779+00:00 app[web.1]: [2022-06-09 01:28:35,036] INFO Setting locking timeout to 10 s (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.069576+00:00 app[web.1]: [2022-06-09 01:28:35,066] INFO Executing schema locking (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.069586+00:00 app[web.1]: [2022-06-09 01:28:35,066] INFO Snapshot step 4 - Determining snapshot offset (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.080765+00:00 app[web.1]: [2022-06-09 01:28:35,080] INFO Snapshot step 5 - Reading structure of captured tables (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.081107+00:00 app[web.1]: [2022-06-09 01:28:35,081] INFO Snapshot step 6 - Persisting schema history (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.087858+00:00 app[web.1]: [2022-06-09 01:28:35,087] INFO Schema locks released. (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.087894+00:00 app[web.1]: [2022-06-09 01:28:35,087] INFO Snapshot step 7 - Snapshotting data (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.088336+00:00 app[web.1]: [2022-06-09 01:28:35,088] INFO Snapshotting contents of 0 tables while still in transaction (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.098247+00:00 app[web.1]: [2022-06-09 01:28:35,098] INFO Snapshot - Final stage (io.debezium.pipeline.source.AbstractSnapshotChangeEventSource)
2022-06-09T01:28:35.104830+00:00 app[web.1]: [2022-06-09 01:28:35,104] INFO Removing locking timeout (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.118107+00:00 app[web.1]: [2022-06-09 01:28:35,118] INFO Snapshot ended with SnapshotResult [status=COMPLETED, offset=SqlServerOffsetContext [sourceInfoSchema=Schema{io.debezium.connector.sqlserver.Source:STRUCT}, sourceInfo=SourceInfo [serverName=heroku_connect, changeLsn=NULL, commitLsn=001d23f3:00016cc0:0001, eventSerialNo=null, snapshot=FALSE, sourceTime=null], snapshotCompleted=true, eventSerialNo=1]] (io.debezium.pipeline.ChangeEventSourceCoordinator)
2022-06-09T01:28:35.118780+00:00 app[web.1]: [2022-06-09 01:28:35,118] WARN After applying the include/exclude list filters, no changes will be captured. Please check your configuration! (io.debezium.relational.RelationalDatabaseSchema)

I'm using SQL Server connector and the logs show Locking captured tables [] - no tables are captured. I've verified my schema, table, and database. I've tried the following, all with topics pre-created.. (also specify all variables from Debezium SQL docs)

  • "table.include.list" : "testTable" && "schema.include.list": "dbo"
  • "table.include.list" : "dbo.testTable" && "schema.include.list": "dbo"
  • "table.include.list" : "DBNAME.dbo.testTable" && "schema.include.list": "dbo"
  • "table.include.list" : "DBNAME.dbo.testTable"
  • "table.include.list" : "dbo.testTable"

Running out of ideas, and no data is captured.. there are thousands of records in the table and its takes ~25min to redeploy docker and cycle thru for tests

2022-06-09T01:28:35.036573+00:00 app[web.1]: [2022-06-09 01:28:35,036] INFO Snapshot step 3 - Locking captured tables [] (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.036779+00:00 app[web.1]: [2022-06-09 01:28:35,036] INFO Setting locking timeout to 10 s (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.069576+00:00 app[web.1]: [2022-06-09 01:28:35,066] INFO Executing schema locking (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.069586+00:00 app[web.1]: [2022-06-09 01:28:35,066] INFO Snapshot step 4 - Determining snapshot offset (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.080765+00:00 app[web.1]: [2022-06-09 01:28:35,080] INFO Snapshot step 5 - Reading structure of captured tables (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.081107+00:00 app[web.1]: [2022-06-09 01:28:35,081] INFO Snapshot step 6 - Persisting schema history (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.087858+00:00 app[web.1]: [2022-06-09 01:28:35,087] INFO Schema locks released. (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.087894+00:00 app[web.1]: [2022-06-09 01:28:35,087] INFO Snapshot step 7 - Snapshotting data (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.088336+00:00 app[web.1]: [2022-06-09 01:28:35,088] INFO Snapshotting contents of 0 tables while still in transaction (io.debezium.relational.RelationalSnapshotChangeEventSource)
2022-06-09T01:28:35.098247+00:00 app[web.1]: [2022-06-09 01:28:35,098] INFO Snapshot - Final stage (io.debezium.pipeline.source.AbstractSnapshotChangeEventSource)
2022-06-09T01:28:35.104830+00:00 app[web.1]: [2022-06-09 01:28:35,104] INFO Removing locking timeout (io.debezium.connector.sqlserver.SqlServerSnapshotChangeEventSource)
2022-06-09T01:28:35.118107+00:00 app[web.1]: [2022-06-09 01:28:35,118] INFO Snapshot ended with SnapshotResult [status=COMPLETED, offset=SqlServerOffsetContext [sourceInfoSchema=Schema{io.debezium.connector.sqlserver.Source:STRUCT}, sourceInfo=SourceInfo [serverName=heroku_connect, changeLsn=NULL, commitLsn=001d23f3:00016cc0:0001, eventSerialNo=null, snapshot=FALSE, sourceTime=null], snapshotCompleted=true, eventSerialNo=1]] (io.debezium.pipeline.ChangeEventSourceCoordinator)
2022-06-09T01:28:35.118780+00:00 app[web.1]: [2022-06-09 01:28:35,118] WARN After applying the include/exclude list filters, no changes will be captured. Please check your configuration! (io.debezium.relational.RelationalDatabaseSchema)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

青巷忧颜 2025-02-12 20:09:10

原来是一个错字,所有这些都按预期工作。确保仅使用

table.include.list:。 < fulltableName>

Turned out to be a typo, all works as expected. Make sure to only use

table.include.list: .*tablename or specify both a schema and table like table.include.list: <schemaname>.<fulltablename>

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文