You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Valentin Kulichenko <va...@gmail.com> on 2015/09/02 22:54:24 UTC
Portable objects
Igniters,
Are portable objects already migrated and will be released as a part of 1.4
(I see that APIs and configuration changes are already in master)? I just
thought it's a pretty big change and we were going to include it only in
1.5, correct me if I'm wrong.
-Val
Re: Portable objects
Posted by Denis Magda <dm...@gridgain.com>.
To be more specific public Portable API is located in the following
packages:
- org.apache.ignite.marshaller.portable package (contains
PortableMarshaller only);
- org.apache.ignite.portable package (PortableObject, PortableBuilder,
PortableMetadata, etc.);
- IgnitePortables interface is placed into org.apache.ignite;
New methods are added to some existed public interfaces:
- Ignite.portables() - returns reference to IgnitePortables interface impl;
- IgniteCache.withKeepPortable() - returns cache instance with
'keepPortable' flag enabled;
- CacheConfiguration.isKeepPortableInStore()/setKeepPortableInStore() -
controls 'keepPortableInStore' flag.
Portable API examples should be merged shortly to 1.4 branch.
--
Denis
On 9/3/2015 8:02 AM, Denis Magda wrote:
> Val,
>
> Yes, the portable API and its implementation is already a part of both
> master and 1.4 branches.
>
> --
> Denis
>
> On 9/2/2015 11:54 PM, Valentin Kulichenko wrote:
>> Igniters,
>>
>> Are portable objects already migrated and will be released as a part
>> of 1.4
>> (I see that APIs and configuration changes are already in master)? I
>> just
>> thought it's a pretty big change and we were going to include it only in
>> 1.5, correct me if I'm wrong.
>>
>> -Val
>>
>
Re: Portable objects
Posted by Denis Magda <dm...@gridgain.com>.
Val,
Yes, the portable API and its implementation is already a part of both
master and 1.4 branches.
--
Denis
On 9/2/2015 11:54 PM, Valentin Kulichenko wrote:
> Igniters,
>
> Are portable objects already migrated and will be released as a part of 1.4
> (I see that APIs and configuration changes are already in master)? I just
> thought it's a pretty big change and we were going to include it only in
> 1.5, correct me if I'm wrong.
>
> -Val
>