# How to return java.util.Date values instead of Long using KafkaJsonSchemaDeserializer with Postgres JDBC source connector?

**URL:** <https://forum.confluent.io/t/how-to-return-java-util-date-values-instead-of-long-using-kafkajsonschemadeserializer-with-postgres-jdbc-source-connector/6187>\
**Category:** Kafka Connect\
**Created:** [5 October 2022 03:35 UTC](https://forum.confluent.io/t/how-to-return-java-util-date-values-instead-of-long-using-kafkajsonschemadeserializer-with-postgres-jdbc-source-connector/6187 "2022-10-05T03:35:01Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sits](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sits](https://forum.confluent.io/u/sits)\
**Post date:** [7 October 2022 06:21 UTC](https://forum.confluent.io/t/how-to-return-java-util-date-values-instead-of-long-using-kafkajsonschemadeserializer-with-postgres-jdbc-source-connector/6187/3 "2022-10-07T06:21:44Z")

</div>

Thanks. I changed to use io.confluent.connect.protobuf.ProtobufConverter and as expected the Kafka consumer now gets a DynamicMessage with the various fields. I was expecting/hoping the timestamp fields would be represented as a google.protobuf.Timestamp object, but instead it was returned as a DynamicMessage with a single field with name google.protobuf.Timestamp.seconds.

Is there some special config required to make this deserialise “properly”? I am using 7.2.1 so I was under the impression this would work based off [Post protobuf schema in Schema Registry - #2 by rick](https://forum.confluent.io/t/post-protobuf-schema-in-schema-registry/1522/2).

---

_[View the full topic](https://forum.confluent.io/t/how-to-return-java-util-date-values-instead-of-long-using-kafkajsonschemadeserializer-with-postgres-jdbc-source-connector/6187)._