If I understand it correctly, Now, this leads to a Long being stored as a NumericField by default whereas previously it would become a String. So, this lead to some confusion.

Right, @Field on a long will now per default be encoded numerically.

I guess we solved the mystery in this case. I probably just merge the Gunnar Morling's pull request as an additional test and resolve this issue.