No matching token for number_type [BIG_INTEGER] on update


#1

I've run into an issue with a bulk update that i'm doing. I have a string field that for some records stores a long string of integers. Based on other similar threads (No matching token for number_type [BIG_INTEGER]), it seems like during the update process the value is being cast into an int, but the int is too large for storage in 64 bits, and the update dies with the eponymous error.

not sure if there is a way around this. I need to be able to store both strings and integers in this field in a way it can be updated later.

I'm surprised that any value mapped as string would ever be returned as an int, and am not sure where to go from here.

We're running 2.2.2


(system) #2