Details
-
Improvement
-
Resolution: Duplicate
-
Critical
-
4.0.0
-
Security Level: Public
Description
In Sherlock, when an index has been partitioned with a WHERE clause, every mutation must be sent to every partition as we don't know the old value and hence cannot direct the update only to the old and new node pair. While we wait for this to be addressed, it would help performance if user can indicate that the fields involved in a WHERE clause are immutable, that is, a given entry cannot move between partitions during an update operation. For such an entry, the updates and deletions will be sent to only the mapped node. As not having this ability currently is a significant performance overhead limiting scalability of partitions, this should be fixed for Sherlock.
Attachments
Issue Links
- relates to
-
MB-15253 support immutable / required constraint on create index partitioning (where clause)
- Resolved