Hi team :wave: , I would like your thoughts on the...
# troubleshooting
i
Hi team 👋 , I would like your thoughts on the approach here. We have existing tables whose dateTimeSpecField is defined as a
LONG
datatype and we would now like to add a timestamp index to that field but realized that the index can only be applied on
TIMESTAMP
datatype. Changing the data type is not a backward compatible change and fails schema update even though the underlying physical value stored is in long format for both. Is the only approach to add a new column and migrate to that column / table with all the data. I was wondering if the index can support datetimespec
LONG
value or the schema update can be done from
LONG
to
TIMESTAMP
instead in-place. Let me know what you think. thanks
m
If you want zero down time, then you'd want to go with the new column approach.
i
Ah gotcha, was trying to avoid that for a minor datatype change but understood the intent on keeping it clean 👍