GitHub user alexandrebrilhante edited a comment on the discussion: Pulsar JDBC
postgres Sink always return null value
I think the issue is that you're sending messages like `{"id": 123, "name":
"John"}` to the sink connector, I think the solution is to exclude the `id`
field from the message, allowing PostgreSQL to auto-generate it.
Can you replicate this issue with a test message like this?
```bash
bin/pulsar-client produce pulsar-postgres-jdbc-sink-topic -m '{"name":
"test"}' -s "\n" -n 100
```
GitHub link:
https://github.com/apache/pulsar/discussions/21298#discussioncomment-10039335
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
