Sam-Serpoosh commented on issue #8761:
URL: https://github.com/apache/hudi/issues/8761#issuecomment-1599967552

   @ad1happy2go Apologies for the delay here, haven't had the chance to check 
on this yet. Will try to get back to you by the end of this week hopefully.
   
   In the meantime, I have a question for you about this ... Given your setup 
and configuration, if you create a similar RDS PostgreSQL table like the one 
I've laid out in [this 
comment](https://github.com/apache/hudi/issues/8761#issue-1716536714) (with the 
same **schema** and everything), and intercept the Kafka messages published by 
Debezium, how would they look like?
   
   Do they look like what I mentioned in that command (also copied below)? Is 
it possible for your to paste a sample message that you see on your end here?
   
   ```json
   {
     "before": null,
     "after": {
       "<TOPIC_PREFIX>.public.samser_customers.Value": {
         "id": 13,
         "name": "Shane",
         "age": 45,
         "created_at": {
           "long": 1684454115314703
         },
         "event_ts": {
           "long": 1683730800000
         }
       }
     },
     "source": {
       "version": "2.2.0.Final",
       "connector": "postgresql",
       "name": "<TOPIC_PREFIX>",
       "ts_ms": 1684454115315,
       "snapshot": {
         "string": "false"
       },
       "db": "<DB_NAME>",
       "sequence": {
         "string": "[\"1303724528456\",\"1303858122816\"]"
       },
       "schema": "public",
       "table": "samser_customers",
       "txId": {
         "long": 816350
       },
       "lsn": {
         "long": 1303858122816
       },
       "xmin": null
     },
     "op": "c",
     "ts_ms": {
       "long": 1684454115349
     },
     "transaction": null
   }
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to