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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/08/08 15:16:20 UTC

[jira] [Assigned] (IGNITE-3654) SpringCache should optionally treat put with null as remove.

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

Vladimir Ozerov reassigned IGNITE-3654:
---------------------------------------

    Assignee: Vladimir Ozerov  (was: Andrew Mashenkov)

> SpringCache should optionally treat put with null as remove.
> ------------------------------------------------------------
>
>                 Key: IGNITE-3654
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3654
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Critical
>             Fix For: 1.8
>
>
> Currently our cache manager delegates put() directly to IgniteCache,put(). This way we do not allow null values. However, other cache providers do allow it. This way users may have troubles when migrating from other caching providers. 
> We should optionally allow null values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)