Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 9 Aug 2016 12:32:29 +0000 (UTC)
From: "Pavel Tupitsyn (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12954512.1459310417000.260212.1470745949400@Atlassian.JIRA>
In-Reply-To: <JIRA.12954512.1459310417000@Atlassian.JIRA>
References: <JIRA.12954512.1459310417000@Atlassian.JIRA> <JIRA.12954512.1459310417245@arcas>
Subject: [jira] [Updated] (IGNITE-2909) Checking cache object type in
 runtime
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 09 Aug 2016 12:32:35 -0000


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

Pavel Tupitsyn updated IGNITE-2909:
-----------------------------------
    Fix Version/s:     (was: 1.7)
                   1.8

> Checking cache object type in runtime
> -------------------------------------
>
>                 Key: IGNITE-2909
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2909
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.5.0.final
>            Reporter: Denis Magda
>            Assignee: Vladislav Pyatkov
>            Priority: Critical
>              Labels: community, important
>             Fix For: 1.8
>
>
> In some cases there is necessity to control a type of object that is being
> inserted into a cache.
> Presently this kind of check is accomplished at compile time only relying
> on Java Generics. However it doesn't prevent us from connecting to a
> cluster using a non-generic instance of a cache and put any kind of data in
> it. This may be not a harmful intention but rather a silly developer mistake.
> It's preferable to rely on the cache interceptor based solution:
> - user will create a generic interceptor that will accept "typeName" in its constructor;
> - class of this interceptor will be placed in the classpath of all the nodes;
> - when a new cache is started statically (Spring cfg) or dynamically this interceptor can be set with a particular allowed "typeName";
> - when interceptor is invoked allowed typeId (taken from allowed "typeName") will be compared with a typeID of a key/value being inserted;
> - exception has to be thrown if allowed typeId is not equal to a key/value typeId being inserted.
> We need to allow to throw exceptions from interceptor and provide an example on how perform type validation using interceptors based approach.
> Refer to the discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Controlling-type-of-object-inserted-in-IgniteCache-td8128.html


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