Hello can you advice if the following error is sti...
# troubleshooting
g
Hello can you advice if the following error is still relevant? When i added metadataTTL to my upsert table i got error saying the comparisonsColumns should be long and found Timestamp, is this relevant or i can ignore it via swagger api?
"Invalid table config: purchases_REALTIME with error: MetadataTTL / DeletedKeysTTL must have comparison column: update_date in numeric type, found: TIMESTAMP"
@Xiang Fu can you advice please?
x
cc: @Jackie I feel we could loose the constraints for TIMESTAMP type?
g
what would the mean? isn't Timestamp just a easier way to represent date time?
My understanding was that once consumed it is converted to long and then compared, as it is stored as long in the segments as far as i understood from docs
x
True, however TIMESTAMP field is not considered as a numeric column from the definition, hence this error.
So we need to consider loose this check
g
alright, in order for me to continue with prod integration i will update the field to long and make it ms since epoch
x
correct, use epoch long value should solve it.
g
Xiang there is one more question not related to this problem but to deepstore integration, can i use this thread about it or i should open a new one?
x
let’s create a new one