ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-3654) SpringCache should optionally treat put with null as remove.
Date Mon, 08 Aug 2016 15:16:20 GMT

     [ 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)

Mime
View raw message