You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
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:
...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:
The text was updated successfully, but these errors were encountered: