This message was deleted.
# generals
Slackbot
06/01/2023, 6:45 AMThis message was deleted.
a
Abhishek Agarwal
06/01/2023, 8:23 AMcan you run with approximation turned off in console? That might be causing this behaviour
a
Ashok Kumar Ragupathi
06/01/2023, 8:24 AMok, let me check. thanks Abhishek.
Ashok Kumar Ragupathi
06/01/2023, 8:28 AMYes, it's showing now same result, after turned off the use count(distinct) approximation. thank you.
what is that approximation does ?
a
Abhishek Agarwal
06/01/2023, 10:17 AMit's a faster way of doing distinct count, at the cost of accuracy.
a
Ashok Kumar Ragupathi
06/01/2023, 10:30 AMok
Ashok Kumar Ragupathi
06/01/2023, 10:30 AMwhile ingest the data, for the date-time value ? whats the data type can set ? is string or long ?
Ashok Kumar Ragupathi
06/01/2023, 10:34 AMI mean apart from __time column another datetime column value.
j
John Kowtko
06/01/2023, 12:57 PMHi Ashok, regarding your second question, this doc page HERE recommends to ingest secondary timestamp fields as LONG in milliseconds format.
a
Ashok Kumar Ragupathi
06/01/2023, 12:58 PMok, John, I tried but it becomes Null value, and If I change to String the datetime show correctly in Load data - data schema step - druid console
Ashok Kumar Ragupathi
06/01/2023, 1:13 PMoh i think it should be in millisecond format ... i just put it as date-time format and tried as Long during ingestion.
j
JRob
06/01/2023, 2:04 PMI've used
timestamp_parsetimestamp_parse("field")a
Ashok Kumar Ragupathi
06/01/2023, 2:05 PMOh ok... thank you JRob