Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.9
-
None
-
None
-
Docs Required, Release Notes Required
Description
Thin client protocol handler for Put_All (1004) operation will create a linked hash map and then invoke putAll on this map.
This leads to couple of issues:
- Thin client may easily deadlock the cluster by issuing parallel transactional putAlls with different order of keys.
- "Unordered map with putAll" warning is printed to log, causing user confusion, even if client actually uses SortedMap with putAll().
What we really need is BinaryObject-aware SortedMap / making sure that keys/KeyCacheObjects are always comparable.
Attachments
Issue Links
- is related to
-
IGNITE-6804 Print a warning if HashMap is passed into bulk update operations
- Resolved