We are using 3.15.1.3.
I went through this link
and it makes sense to change this field to last-update-time. Thanks for the suggestion.
In our case, Record is getting updated more than 64k but still generation is less than 64k. I guess that because of generation rolling policy.
Now, we have another issue related to this, in our Java client, where we are trying to find record insert/update based on the generation number returned by the client. As per your suggestion, we may end up in getting record generation number as 1 multiple times. In this case, how should we rely on the java client to find that the transaction is insert/update? Our counters went bad with this client logic.