[jira] [Comment Edited] (IGNITE-11300) MVCC: forbid using DataStreamer with allowOverwrite=true

["Ivan Pavlukhin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-11300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767211#comment-16767211 ] 

Ivan Pavlukhin edited comment on IGNITE-11300 at 2/27/19 2:16 PM:
------------------------------------------------------------------

[~amashenkov], {{allowOverwrite=true}} have not been explicitly tested. Moreover, streamer implementation using single {{cache.put}} operations will most likely have very poor performance.

{{allowOverwrite=false}} should be addressed in scope of IGNITE-9314. Currently, streamer in such mode will not insert a tuple if there is anything (e.g. aborted versions) for a given key in BPlusTree.


was (Author: pavlukhin):
[~amashenkov], {{allowOverwrite=true}} have not been explicitly tested. Moreover, streamer implementation using single {{cache.put}} operations will most likely have very poor performance.

{{allowOverwrite=false}} should be addressed in scope of IGNITE-9314. Currently, streamer in such mode will not insert a tuple if there is anything (e.g. aborted versions) for a give key in BPlusTree.

> MVCC: forbid using DataStreamer with allowOverwrite=true
> --------------------------------------------------------
>
>                 Key: IGNITE-11300
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11300
>             Project: Ignite
>          Issue Type: Task
>          Components: mvcc
>    Affects Versions: 2.7
>            Reporter: Ivan Pavlukhin
>            Priority: Major
>             Fix For: 2.8
>
>
> Calling {{IgniteDataStreamer.allowOverwrite(true)}} configures a streamer to use single-key cache put/remove operations for data modification. But put/remove operations on MVCC caches can be aborted due to write conflicts. So, some development effort is needed to support that mode properly. Let's throw exception in such case for MVCC caches.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)