[
https://issues.apache.org/jira/browse/IGNITE-20669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov updated IGNITE-20669:
-----------------------------------
Epic Link: IGNITE-21174
> The optimal solution is to use BitSet instead of collecting NullBinaryRow in
> the replica response
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-20669
> URL: https://issues.apache.org/jira/browse/IGNITE-20669
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> We have unified access to replica responses, but it also increases the
> response size. Bitset might be used to optimize the response message size.
> This is relevant for batch operations: _insertAll_, _deleteAll _ and
> _deleteAllExact_.
> h3. Implementation notes
> All of the operations use the snipped:
> {code}
> if (rowIsApplied()) {
> result.add(new NullBinaryRow());
> } else {
> result.add(null);
> }
> {code}
> the better way to use _BitSet_ here.
> h3. Definition of done
> Operations: {{RW_DELETE_EXACT_ALL}}, {{RW_INSERT_ALL}} and {{RW_DELETE_ALL}}
> return _BitSet_ in the replica result. Class _NullBinaryRow_ is not needed
> more and can be deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
