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

Posted to issues@ignite.apache.org by "Uday Kale (JIRA)" <ji...@apache.org> on 2019/05/01 15:00:00 UTC

[jira] [Updated] (IGNITE-11828) "operationContextPerCall" is set only during the moment of Ignite binary queue creation

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

Uday Kale updated IGNITE-11828:
-------------------------------
    Summary: "operationContextPerCall" is set only during the moment of Ignite binary queue creation  (was: Ignite Queue "operationContextPerCall" is set only during the moment of creation)

> "operationContextPerCall" is set only during the moment of Ignite binary queue creation
> ---------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11828
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11828
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Uday Kale
>            Assignee: Uday Kale
>            Priority: Major
>
> "operationContextPerCall" is a thread-local entity used for cache operations. It is set before any specific cache operation (get / put / ...) and cleared after. This way cache has the ability to read all specific settings and work as desired. More specifically - it allows having both "keepBinary" and "not keepBinary" data structures on the same cache in the same thread.
> In current implementation of queue the "operationContextPerCall" is only set during the time of creation. All queues and sets become "keepBinary" structures in current thread but remain "not keepBinary" in other.



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