This is the configuration currently in use
--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/90c15155-504a-4c6f-a85f-d5b0a99a9ae3n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/182bb315-930f-4210-951d-009a181f3a00n%40googlegroups.com.
Oh, sorry, I thought you meant extra configuration, table.include.list and schema.include.list are both available. SchemaList is the user and tableList is the table. Currently there are only two tables in the tableList.
Complete configuration information is as follows
properties.setProperty("database.tablename.case.insensitive", "false");
properties.setProperty("log.mining.strategy", "online_catalog");
properties.setProperty("log.mining.continuous.mine", "true");
properties.setProperty("scan.startup.mode", "latest-offset");
properties.setProperty("log.mining.batch.size.max","200000");
properties.setProperty("log.mining.batch.size.min","150000");
DebeziumSourceFunction<String> sourceFunction = OracleSource.<String>builder().
hostname("")
.port()
.database("")
.username("")
.password("")
.schemaList("user")
.tableList("user.table,user.table")
.debeziumProperties(properties)
.deserializer(new orDeserializationSchema())
.startupOptions(StartupOptions.initial())
.build();
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/51280f6d-8840-4b0c-b85c-06db729028b1n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/7b804ec7-abe6-4c3c-a7c0-16dc12258578n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/4dad625f-a815-449f-a47d-066a872bd11an%40googlegroups.com.
This is the data from the SQL query you provided
This is the data from another query
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/fc2f02bf-6a92-4440-acac-72b797acfdean%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/2102eccd-c38b-4ecb-8f18-6ee086047123n%40googlegroups.com.
Hi
The log information has been sent to you separately. This is part of the log I captured from the log. Do you want to run all the logs for several hours? Because the whole log is too large. If you want the whole thing, I'll be more prepared for you next time
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/8bfc8ea2-7a98-4043-bea6-906aea480777n%40googlegroups.com.
Hi,
I have understood the problem you mentioned. We just started to speculate that the reason for the problem is the same. We have a lot of users in our database, and we need a small amount of data. The amount of data collected is too large because other users are constantly operating and we don't need a lot of that data.
Would adding DeBezium configuration information solve your problem of reducing data collection based on user exclusion of specific transactions? I don't see that DeBezium has any configuration information about it. Do you want us to start from the database? Split this user out of the current database?
If we can solve the problem of mining only specific users' information, then we won't be mining millions of rows and only a few of them are relevant to us.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/9cf91292-f27e-4301-baec-b4ed3b51c550n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/7c8e7457-5d06-4f92-b3fb-5d9f36eff10fn%40googlegroups.com.
This method has been modified in the Github Master branch, but remains in the release-2.2 branch, and in the Maven repository in version 2.2.1.
We noticed that they modified the master branch last month and the release-2.2 branch ten months ago.
The last date of version 2.2.1 in Maven repository is also in April, and Flink should not be caused by the new release version.
Github flink Site
https://github.com/ververica/flink-cdc-connectors/tree/master
Maven Repository Address
https://mvnrepository.com/artifact/com.ververica/flink-connector-debezium
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/6e2f17f3-5bce-4fb2-980e-311880e80862n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/bccf6aac-38ff-4b1e-9522-a16deb0ebdfcn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/3f162ef0-fcb0-4d22-bd2a-1deba3521df5n%40googlegroups.com.