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
When we create a LiteralKeyExpression using Java objects (instead of passing an existing Protobuf), we use the LiteraKeyExpression.toProtoValue() method to create a serialized form, which is used (among other things) for the LiteralKeyExpressions equals() method.
Currently, all numeric types, including integers, are converted to floating point values in this serialization.
The text was updated successfully, but these errors were encountered:
A similar (but less subtle) issue shows up with LiteralKeyExpressions of byte arrays. When we deserialize the serialized form, we produce a LiteralKeyExpression of ByteString rather than byte[].
…incorrect.
Previously, serializing certain LiteralKeyExpressions (of type Long
or byte[]) would produce a Protobuf that, when deserialized, would
not contain a value of a different type (Float or ByteString,
respectively). This fixesFoundationDB#756 and adds some tests that should
give us more confidence that the serialization is correct.
When we create a
LiteralKeyExpression
using Java objects (instead of passing an existing Protobuf), we use theLiteraKeyExpression.toProtoValue()
method to create a serialized form, which is used (among other things) for theLiteralKeyExpression
sequals()
method.Currently, all numeric types, including integers, are converted to floating point values in this serialization.
The text was updated successfully, but these errors were encountered: