Hi Jiri,
Please find the attached server logs and application.properties file.
Thanks,
Laxinandan Rajkhowa
From: debe...@googlegroups.com <debe...@googlegroups.com>
On Behalf Of jiri.p...@gmail.com
Sent: Wednesday, June 12, 2024 5:20 PM
To: debezium <debe...@googlegroups.com>
Subject: [debezium] Re: Debezium-Pub/Sub publish to multiple topic issue
[Email from a non-Nagarro source: please exercise caution with links and attachments]
--
You received this message because you are subscribed to a topic in the Google Groups "debezium" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/debezium/qbHuFToXuUA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
debezium+u...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/debezium/1987e156-37ca-437b-a88d-c56ca982d84bn%40googlegroups.com.
Hi Jiri,
I am pleased to inform that the issue is resolved after adding the debezium-scripting-2.6.2.Final.jar to Debezium Environment.
Thank You for the suggestion !! 😊
However, I also want to discuss on another issue. The message sent to Pub/Sub has schema details and payload. We only want the payload to be sent and not schema details. The green shaded text is the payload.
We have added the “debezium.source.transforms.wrap.type=io.debezium.transforms.ExtractNewRecordState” in application.properties and is not working.
Can you please suggest a solution for this.
Message Body:
{"schema":{"type":"struct","fields":[{"type":"string","optional":false,"field":"id"},{"type":"string","optional":true,"field":"aggregate_id"},{"type":"string","optional":true,"field":"aggregate_type"},
{"type":"string","optional":true,"field":"created_by"},{"type":"int64","optional":false,"name":"io.debezium.time.Timestamp","version":1,"field":"created_on"},{"type":"string","optional":true,"field":"event_type"},
{"type":"string","optional":true,"field":"payload"}],"optional":false,"name":"outbox.outbox.outbox_event.Value"},
"payload":{"id":"24242","aggregate_id":"23222","aggregate_type":"com.nagarro.oms.common.audit.AuditDomainEvent","created_by":
"System","created_on":1718236800000,"event_type":"com.nagarro.oms.common.audit.AuditDomainEvent","payload":"Nagarro"}}
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/e695680d-0734-470f-bb95-7fd1ed43e736n%40googlegroups.com.
Hi Jiri,
Thanks!!
We are facing another issue and need your suggestion.
Debezium is working fine in my local. But if I deploy debezium to another machine then it’s not working. I have also cleared schistory.dat and offsets.dat files.
Problem Statement:
Debezium is trying to capture events from all schemas rather than single table. Due to this the logs has exception. We have to capture events from outbox.outbox_event table only.
Attached the server logs and application.properties.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/34ba3f5e-bcd4-4644-8137-6e55688313e9n%40googlegroups.com.
Hi Jiri,
Thank You!!
We are able to resolve the issues with MySQL Database and working as expected.
However, we have another requirement to integrate Debezium with PostgreSQL and Pub/Sub.
And facing below issues and need your suggestion:
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/dc61e732-c982-4d80-aee2-aad5f4368c59n%40googlegroups.com.
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/SEZPR06MB531739132F96F9781F29A9D3E8CE2%40SEZPR06MB5317.apcprd06.prod.outlook.com.
Hi Chris,
As per our requirement, we have to connect to AlloyDB in GCP.
Problem Statement:
After doing the changes, the events are not captured by Debezium.
Attaching the server logs and application.properties. We have used pgoutput in application.properties.
We have configured AlloyDB with below changes. Please let us know if any additional changes are required.
3. ALTER ROLE postgres WITH REPLICATION LOGIN;
CREATE ROLE replication_role WITH REPLICATION LOGIN;
CREATE USER debezium_user WITH PASSWORD 'password';
GRANT debezium TO postgres;
CREATE ROLE replication_group WITH LOGIN;
GRANT replication_group TO postgres;
GRANT replication_group TO debezium_user;
ALTER TABLE outbox.outbox_event OWNER TO replication_group;
Thanks,
Laxinandan Rajkhowa
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/d95eea83-254c-4843-8a92-79a14b99ff2a%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/SEZPR06MB53179C516C6FA50F2323CAD6E8C82%40SEZPR06MB5317.apcprd06.prod.outlook.com.
Hi Chris,
Thanks!!
Issue is resolved after removing “database.include.list”
Another question. We have deployed debezium to VM(Ubuntu OS) and from SSH terminal ran the ./run.sh to start debezium. However, after the SSH session is closed, the debezium server also stops.
Any better way to trigger the ./run.sh script.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/b8655ea5-adee-4da1-94dd-011eff002ecc%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/SEZPR06MB53178908B066AA1CF63B1C49E8C82%40SEZPR06MB5317.apcprd06.prod.outlook.com.