You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2022/06/03 06:31:00 UTC

[jira] [Updated] (IGNITE-16022) Thin 3.0: Optimize multi-row responses using guaranteed order

     [ https://issues.apache.org/jira/browse/IGNITE-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Sapego updated IGNITE-16022:
---------------------------------
    Fix Version/s: 3.0.0-alpha6
                       (was: 3.0.0-alpha5)

> Thin 3.0: Optimize multi-row responses using guaranteed order
> -------------------------------------------------------------
>
>                 Key: IGNITE-16022
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16022
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>
> IGNITE-16004 introduces guaranteed row order for multi-row operations, like *GetAll*, *InsertAll*, *DeleteAll*. We can leverage this fact to optimize the thin client protocol:
> * *GetAll* can return values without keys (keys are known on the client), and without size (it is the same as input collection size)
> * *InsertAll* and *DeleteAll* can return a bit set to indicate which items were skipped.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)