Hi Team, I was trying out "comparisonColumn" conf...
# troubleshooting
a
Hi Team, I was trying out "comparisonColumn" config of upsertConfig, it seems like table config is not accepting this config. after updating the table config, config is still the same like below. "upsertConfig": { "mode": "FULL" }, Also I tried pushing old transaction date time record into real-time, and it got updated with that new record. Which shouldn't have. Can someone please help?
m
how did you try to update the config, through the UI?
a
yes @Mark Needham. also just to inform. i had added this transaction datetime as dimension. i am bit confused, it should be dimension or it should in datetimeFieldSpec.
m
for datetime columns, you want them to be under
dateTimeFieldSpecs
I'm not sure why the
comparisonColumn
update isn't working - do you see any error message in the controller logs?
logs/pinot-all.log
a
checking logs
Hey @Mark Needham, I have secondary time column which i want to use for comparison, it have data till millisecond. What should the granularity of this column in shcema?
m
I think that granularity would be fine
a
Hey @Mark Needham, can't find anything on logs of controller.
Hey @Mayank , comparison config issue.
m
Anish and I tried the swagger UI to upload the table config, it returned 200, however, did not update the comparison column config. One possibility is that that config is not available in the code that is deployed (0.8). cc: @Yupeng Fu @Jackie
j
@Mayank
comparisonColumn
support is added in
0.9.0
m
Thanks for confirming @Jackie. That’s what I thought
a
thanks guys for confirming.