You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Beyond #2141 there is actually bigger problem that very long BigIntegers are slow to coerce/convert into other types.
One example is that Enums may be deserialized from integers, and although eventual type expected is int, integral numbers longer than maximum that fits in long (22+ digits or whatever limit is) are decoded as BigIntegers. And although bounds-checks will catch the problem eventually, turns out that performance issue is severe during processing.
So... we should catch this at lower layer, at least for textual formats.
The text was updated successfully, but these errors were encountered:
(note: possibly belongs to
jackson-core
)Beyond #2141 there is actually bigger problem that very long
BigInteger
s are slow to coerce/convert into other types.One example is that
Enum
s may be deserialized from integers, and although eventual type expected isint
, integral numbers longer than maximum that fits inlong
(22+ digits or whatever limit is) are decoded asBigInteger
s. And although bounds-checks will catch the problem eventually, turns out that performance issue is severe during processing.So... we should catch this at lower layer, at least for textual formats.
The text was updated successfully, but these errors were encountered: