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
create table CREATE TABLE timestamp_table WITH (kafka_topic='timestamp-test', value_format='AVRO', KEY='UUID');
get the table info
ksql> describe extended timestamp_table;
Name : TIMESTAMP_TABLE
Type : TABLE
Key field : UUID
Key format : STRING
Timestamp field : Not set - using <ROWTIME>
Value format : AVRO
Kafka topic : timestamp-test (partitions: 1, replication: 1)
Field | Type
---------------------------------------------------------------------------------------------------------
ROWTIME | BIGINT (system)
ROWKEY | VARCHAR(STRING) (system)
UUID | VARCHAR(STRING)
USERID | INTEGER
ORGANISATIONID | INTEGER
TIMESTAMP | INTEGER
TYPE | VARCHAR(STRING)
PAYLOAD | STRUCT<STARTTIME INTEGER, ENDTIME INTEGER, DEVICEID INTEGER, METADATA VARCHAR(STRING)>
---------------------------------------------------------------------------------------------------------
Local runtime statistics
------------------------
(Statistics of the local KSQL server interaction with the Kafka topic timestamp-test)
As you can see, records are inserted, format in known, uuid has type string and match the rowkey
This is the currently expected behavior for a SELECT * on a table, as it is a continuous query on the table which will therefore also show subsequent changes to the table (and to keys).
The feature request to add the functionality you described is tracked at #530. Feel free to upvote (+1) that ticket.
CREATE TABLE timestamp_table WITH (kafka_topic='timestamp-test', value_format='AVRO', KEY='UUID');
As you can see ids in the list are duplicated.
The text was updated successfully, but these errors were encountered: