Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.0.0-beta1
-
Docs Required, Release Notes Required
Description
Currently, we calculate colocation hash separately (see ClientTable.doSchemaOutInOpAsync), and then serialize the data into BinaryTuple.
This causes double work:
- Extract columns from the user-provided object (POJO or Tuple)
- Extract value bytes (for some types like strings) - expensive and allocates an array
Instead, we can calculate the colocation hash while serializing the data into a BinaryTuple, like the C# client does.
Attachments
Issue Links
- is related to
-
IGNITE-19914 .NET: Thin 3.0: Colocation column order is not preserved
- Resolved
-
IGNITE-19935 Allow combining individual colocation hashes
- Resolved