Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ksqldb returning TIMESTAMP in wrong format. #10638

Open
credmond opened this issue Jan 12, 2025 · 0 comments
Open

ksqldb returning TIMESTAMP in wrong format. #10638

credmond opened this issue Jan 12, 2025 · 0 comments

Comments

@credmond
Copy link

If a stream/table has a TIMESTAMP column, and the REST API'S /query will return with JSON reporting it as a timestamp.

This is a string value, and is of the wrong format. As per https://docs.confluent.io/platform/current/ksqldb/reference/sql/data-types.html:

image

...it needs to map to java.sql.Timestamp.

E.g, there can be a "T" separator in there, so it is NOT compatible with java.sql.Timestamp despite what the documentation says. But the response contains it. E.g., "1970-01-01T03:25:43.335".

Shouldn't it be impossible?

Example response:

{"queryId":"transient_TICKET_SALES_6527111408917527410","columnNames":["PURCHASER_NAME","MOVIE_TITLE","TICKET_DATE","SHOWTIME","PURCHASE_TIMESTAMP","LOCATION"],"columnTypes":["STRING","STRING","DATE","TIME","TIMESTAMP","STRING"]}
["Alice","blah","2003-10-20","00:00:12","1970-01-01T03:25:43.335","location"]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant