You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Paulo Pires <pi...@littlebits.cc> on 2015/12/07 00:32:27 UTC
Serialization issue with Ignite 1.5 built from master (357d791)
Hi,
I have the following class http://pastebin.com/QD4tmH29 and while it works
fine with 1.4.0 it is not working with 1.5 built from source. The error is:
java.lang.ClassCastException: java.util.HashMap cannot be cast to
xxx.DeviceSubscriptionFilterMap
Ideas?
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
I am OK with building my own version.
Thank you,
Pires
On Tue, Jan 19, 2016 at 10:47 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Paulo,
>
> Any reason why you need a hot fix release? Looks like Alexey provided you
> with a commit revision number you can build from. Should not be hard to
> generate your own release jar.
>
> D.
>
> On Fri, Jan 15, 2016 at 1:24 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> Thank you Alexey.
>>
>> Any ETA on a hotfix release?
>>
>> Cheers,
>> Pires
>>
>> On Fri, Jan 15, 2016 at 7:37 AM, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com> wrote:
>>
>>> Paulo,
>>>
>>> The issue has been fixed and the fix was merged to master. You should be
>>> able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and
>>> build Ignite from sources with this fix.
>>>
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Paulo,
Any reason why you need a hot fix release? Looks like Alexey provided you
with a commit revision number you can build from. Should not be hard to
generate your own release jar.
D.
On Fri, Jan 15, 2016 at 1:24 AM, Paulo Pires <pi...@littlebits.cc> wrote:
> Thank you Alexey.
>
> Any ETA on a hotfix release?
>
> Cheers,
> Pires
>
> On Fri, Jan 15, 2016 at 7:37 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
>> Paulo,
>>
>> The issue has been fixed and the fix was merged to master. You should be
>> able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and
>> build Ignite from sources with this fix.
>>
>>
>>
>
>
> --
> Cheers,
> Pires
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
Thank you Alexey.
Any ETA on a hotfix release?
Cheers,
Pires
On Fri, Jan 15, 2016 at 7:37 AM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Paulo,
>
> The issue has been fixed and the fix was merged to master. You should be
> able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and
> build Ignite from sources with this fix.
>
>
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
Paulo,
The issue has been fixed and the fix was merged to master. You should be
able to cherry-pick the commit 02dbcfd8ed2701a4f415c8871d0b8fd08bfa0583 and
build Ignite from sources with this fix.
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Is it also possible that we create a branch with this fix and provide it
here?
On Tue, Jan 12, 2016 at 10:07 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Alexey,
>>
>> Do you mean this?
>>
>> class MyWrapper {
>> // Wrapped map.
>> Map<> myMap = …;
>> }
>>
>
> Yes, this is exactly what I meant.
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
>
> Alexey,
>
> Do you mean this?
>
> class MyWrapper {
> // Wrapped map.
> Map<> myMap = …;
> }
>
Yes, this is exactly what I meant.
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Alexey,
Do you mean this?
class MyWrapper {
// Wrapped map.
Map<> myMap = …;
}
D.
On Tue, Jan 12, 2016 at 10:25 AM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Paulo,
>
> Not sure if this will work for you as a workaround, but you can create a
> thin wrapper around your map and put it into the cache instead. In this
> case the map type is preserved.
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
Paulo,
Not sure if this will work for you as a workaround, but you can create a
thin wrapper around your map and put it into the cache instead. In this
case the map type is preserved.
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
Dmitriy,
For the lack of a workaround that will do it.
But I can wait for a week or two before releasing my software. Do you think
it will take more time than that?
Thank you,
Pires
On Tue, Jan 12, 2016 at 6:09 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> Paulo,
>
> We probably won’t be able to release it quickly, but we can tag the fix
> for you in GIT, and you can do your own build from it. Will that work?
>
> D.
>
> On Tue, Jan 12, 2016 at 9:10 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> Hi Alexey,
>>
>> Is there any workaround I can use to circumvent this?
>>
>> If not, can you please release this as 1.5.1? Seems like a high/critical
>> bug to me.
>>
>> Cheers,
>> Pires
>>
>> On Tue, Jan 12, 2016 at 4:46 PM, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com> wrote:
>>
>>> Thanks Paulo,
>>>
>>> I've reproduced the issue. Turned out the tests we have added were not
>>> enough to cover all the cases. I fixed this behavior and now waiting for
>>> the CI. I have reopened corresponding ticket:
>>> https://issues.apache.org/jira/browse/IGNITE-2099
>>>
>>> Let community decide when and how this fix should be released.
>>>
>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Dmitriy Setrakyan <ds...@apache.org>.
Paulo,
We probably won’t be able to release it quickly, but we can tag the fix for
you in GIT, and you can do your own build from it. Will that work?
D.
On Tue, Jan 12, 2016 at 9:10 AM, Paulo Pires <pi...@littlebits.cc> wrote:
> Hi Alexey,
>
> Is there any workaround I can use to circumvent this?
>
> If not, can you please release this as 1.5.1? Seems like a high/critical
> bug to me.
>
> Cheers,
> Pires
>
> On Tue, Jan 12, 2016 at 4:46 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
>> Thanks Paulo,
>>
>> I've reproduced the issue. Turned out the tests we have added were not
>> enough to cover all the cases. I fixed this behavior and now waiting for
>> the CI. I have reopened corresponding ticket:
>> https://issues.apache.org/jira/browse/IGNITE-2099
>>
>> Let community decide when and how this fix should be released.
>>
>
>
>
> --
> Cheers,
> Pires
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
Hi Alexey,
Is there any workaround I can use to circumvent this?
If not, can you please release this as 1.5.1? Seems like a high/critical
bug to me.
Cheers,
Pires
On Tue, Jan 12, 2016 at 4:46 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Thanks Paulo,
>
> I've reproduced the issue. Turned out the tests we have added were not
> enough to cover all the cases. I fixed this behavior and now waiting for
> the CI. I have reopened corresponding ticket:
> https://issues.apache.org/jira/browse/IGNITE-2099
>
> Let community decide when and how this fix should be released.
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
Thanks Paulo,
I've reproduced the issue. Turned out the tests we have added were not
enough to cover all the cases. I fixed this behavior and now waiting for
the CI. I have reopened corresponding ticket:
https://issues.apache.org/jira/browse/IGNITE-2099
Let community decide when and how this fix should be released.
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
Hi Alexey,
https://github.com/pires/ignite-1.5-serialization-issue/tree/master
All you need is to run mvn test.
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.362 sec
<<< FAILURE!
test_get(com.github.pires.MyMapTest) Time elapsed: 0.006 sec <<< FAILURE!
java.lang.ClassCastException: java.util.HashMap cannot be cast to
com.github.pires.MyMap
at com.github.pires.MyMapTest.test_get(MyMapTest.java:60)
On Mon, Jan 11, 2016 at 5:14 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Paulo,
>
> This should have been fixed - corresponding marshaller tests have been
> added, I have just verified this. Can you please share your configuration,
> full node logs and a small code snippet that shows how to reproduce the
> issue?
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
Paulo,
This should have been fixed - corresponding marshaller tests have been
added, I have just verified this. Can you please share your configuration,
full node logs and a small code snippet that shows how to reproduce the
issue?
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
OptimizedMarshaller doesn't work as well.
igniteConfig.setMarshaller(new OptimizedMarshaller());
On Mon, Jan 11, 2016 at 12:59 PM, Paulo Pires <pi...@littlebits.cc> wrote:
> The following does not work.
>
> private void writeObject(ObjectOutputStream s)
> throws IOException {
> s.defaultWriteObject();
> }
>
> On Mon, Jan 11, 2016 at 12:54 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> 1.5.0.final doesn't fix this. Is there a way I can use 1.5.0.final?
>>
>> On Mon, Dec 7, 2015 at 10:33 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
>> > wrote:
>>
>>> I absolutely agree with Valentin on this. We should make sure that we
>>> support Java serialization without any omissions. Can this be fixed quickly
>>> before 1.5 GA is out?
>>>
>>> D.
>>>
>>> On Mon, Dec 7, 2015 at 11:12 AM, Valentin Kulichenko <
>>> valentin.kulichenko@gmail.com> wrote:
>>>
>>>> Alex,
>>>>
>>>> I don't like this. I think both marshallers should behave in the same
>>>> way and this behavior should be consistent with Java serialization spec. I
>>>> hardly believe that classes like in Paulo's example will be used for
>>>> communication with .NET/C++. And I would prefer to have such restrictions
>>>> for interop, rather than for Java-only scenario.
>>>>
>>>> -Val
>>>>
>>>> On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <
>>>> alexey.goncharuk@gmail.com> wrote:
>>>>
>>>>> Paulo,
>>>>>
>>>>> After a closer look I see that BinaryMarshaller works the way it was
>>>>> designed to work. The issue is that your class implements Map and
>>>>> Serializable, but does not define writeObject(), that's why Ignite
>>>>> serializes it in the portable format discarding information about the
>>>>> custom user type (this way it can be read in other platforms - .NET and C++)
>>>>>
>>>>> There are two ways to solve this. First is to set OptimizedMarshaller
>>>>> in configuration (this marshaller was the default marshaller in
>>>>> ignite-1.4). The second one would be to define writeObject() method in your
>>>>> class which will call defaultWriteObject, like this:
>>>>>
>>>>> private void writeObject(ObjectOutputStream s)
>>>>> throws IOException {
>>>>> s.defaultWriteObject();
>>>>> }
>>>>>
>>>>> I am also curious what other community members think about current
>>>>> behavior.
>>>>>
>>>>> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>>>>>
>>>>>> With 3fbf3e9 the issue is still there.
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Paulo,
>>>>>>>
>>>>>>> I see commit with fix in master branch.
>>>>>>>
>>>>>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>>>>>> Author: Alexey Goncharuk <al...@gmail.com>
>>>>>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>>>>>
>>>>>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>>>>>
>>>>>>>
>>>>>>> Could you please make sure that you have codebase with this commit
>>>>>>> and repeat your test?
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Andrey,
>>>>>>>>
>>>>>>>> This is great news! While marked as fixed, it doesn't seem to have
>>>>>>>> hit the Github clone repo. Am I missing something? Would like to keep on
>>>>>>>> testing 1.5 before it gets released.
>>>>>>>>
>>>>>>>> Pires
>>>>>>>>
>>>>>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Paulo,
>>>>>>>>>
>>>>>>>>> it is know issue (see JIRA ticket
>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>>>>>
>>>>>>>>> The problem is fixed and fix will be included into nearest
>>>>>>>>> ignite-1.5 release.
>>>>>>>>>
>>>>>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I have the following class http://pastebin.com/QD4tmH29 and
>>>>>>>>>> while it works fine with 1.4.0 it is not working with 1.5 built from
>>>>>>>>>> source. The error is:
>>>>>>>>>>
>>>>>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>>>>>
>>>>>>>>>> Ideas?
>>>>>>>>>> --
>>>>>>>>>> Cheers,
>>>>>>>>>> Pires
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Andrey Gura
>>>>>>>>> GridGain Systems, Inc.
>>>>>>>>> www.gridgain.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Pires
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Andrey Gura
>>>>>>> GridGain Systems, Inc.
>>>>>>> www.gridgain.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>> Pires
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
>
> --
> Cheers,
> Pires
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
The following does not work.
private void writeObject(ObjectOutputStream s)
throws IOException {
s.defaultWriteObject();
}
On Mon, Jan 11, 2016 at 12:54 PM, Paulo Pires <pi...@littlebits.cc> wrote:
> 1.5.0.final doesn't fix this. Is there a way I can use 1.5.0.final?
>
> On Mon, Dec 7, 2015 at 10:33 PM, Dmitriy Setrakyan <ds...@apache.org>
> wrote:
>
>> I absolutely agree with Valentin on this. We should make sure that we
>> support Java serialization without any omissions. Can this be fixed quickly
>> before 1.5 GA is out?
>>
>> D.
>>
>> On Mon, Dec 7, 2015 at 11:12 AM, Valentin Kulichenko <
>> valentin.kulichenko@gmail.com> wrote:
>>
>>> Alex,
>>>
>>> I don't like this. I think both marshallers should behave in the same
>>> way and this behavior should be consistent with Java serialization spec. I
>>> hardly believe that classes like in Paulo's example will be used for
>>> communication with .NET/C++. And I would prefer to have such restrictions
>>> for interop, rather than for Java-only scenario.
>>>
>>> -Val
>>>
>>> On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <
>>> alexey.goncharuk@gmail.com> wrote:
>>>
>>>> Paulo,
>>>>
>>>> After a closer look I see that BinaryMarshaller works the way it was
>>>> designed to work. The issue is that your class implements Map and
>>>> Serializable, but does not define writeObject(), that's why Ignite
>>>> serializes it in the portable format discarding information about the
>>>> custom user type (this way it can be read in other platforms - .NET and C++)
>>>>
>>>> There are two ways to solve this. First is to set OptimizedMarshaller
>>>> in configuration (this marshaller was the default marshaller in
>>>> ignite-1.4). The second one would be to define writeObject() method in your
>>>> class which will call defaultWriteObject, like this:
>>>>
>>>> private void writeObject(ObjectOutputStream s)
>>>> throws IOException {
>>>> s.defaultWriteObject();
>>>> }
>>>>
>>>> I am also curious what other community members think about current
>>>> behavior.
>>>>
>>>> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>>>>
>>>>> With 3fbf3e9 the issue is still there.
>>>>>
>>>>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com>
>>>>> wrote:
>>>>>
>>>>>> Paulo,
>>>>>>
>>>>>> I see commit with fix in master branch.
>>>>>>
>>>>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>>>>> Author: Alexey Goncharuk <al...@gmail.com>
>>>>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>>>>
>>>>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>>>>
>>>>>>
>>>>>> Could you please make sure that you have codebase with this commit
>>>>>> and repeat your test?
>>>>>>
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Andrey,
>>>>>>>
>>>>>>> This is great news! While marked as fixed, it doesn't seem to have
>>>>>>> hit the Github clone repo. Am I missing something? Would like to keep on
>>>>>>> testing 1.5 before it gets released.
>>>>>>>
>>>>>>> Pires
>>>>>>>
>>>>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Paulo,
>>>>>>>>
>>>>>>>> it is know issue (see JIRA ticket
>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>>>>
>>>>>>>> The problem is fixed and fix will be included into nearest
>>>>>>>> ignite-1.5 release.
>>>>>>>>
>>>>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I have the following class http://pastebin.com/QD4tmH29 and while
>>>>>>>>> it works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>>>>>> error is:
>>>>>>>>>
>>>>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>>>>
>>>>>>>>> Ideas?
>>>>>>>>> --
>>>>>>>>> Cheers,
>>>>>>>>> Pires
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Andrey Gura
>>>>>>>> GridGain Systems, Inc.
>>>>>>>> www.gridgain.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Pires
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andrey Gura
>>>>>> GridGain Systems, Inc.
>>>>>> www.gridgain.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Pires
>>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> Cheers,
> Pires
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
1.5.0.final doesn't fix this. Is there a way I can use 1.5.0.final?
On Mon, Dec 7, 2015 at 10:33 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:
> I absolutely agree with Valentin on this. We should make sure that we
> support Java serialization without any omissions. Can this be fixed quickly
> before 1.5 GA is out?
>
> D.
>
> On Mon, Dec 7, 2015 at 11:12 AM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
>> Alex,
>>
>> I don't like this. I think both marshallers should behave in the same way
>> and this behavior should be consistent with Java serialization spec. I
>> hardly believe that classes like in Paulo's example will be used for
>> communication with .NET/C++. And I would prefer to have such restrictions
>> for interop, rather than for Java-only scenario.
>>
>> -Val
>>
>> On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com> wrote:
>>
>>> Paulo,
>>>
>>> After a closer look I see that BinaryMarshaller works the way it was
>>> designed to work. The issue is that your class implements Map and
>>> Serializable, but does not define writeObject(), that's why Ignite
>>> serializes it in the portable format discarding information about the
>>> custom user type (this way it can be read in other platforms - .NET and C++)
>>>
>>> There are two ways to solve this. First is to set OptimizedMarshaller in
>>> configuration (this marshaller was the default marshaller in ignite-1.4).
>>> The second one would be to define writeObject() method in your class which
>>> will call defaultWriteObject, like this:
>>>
>>> private void writeObject(ObjectOutputStream s)
>>> throws IOException {
>>> s.defaultWriteObject();
>>> }
>>>
>>> I am also curious what other community members think about current
>>> behavior.
>>>
>>> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>>>
>>>> With 3fbf3e9 the issue is still there.
>>>>
>>>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com>
>>>> wrote:
>>>>
>>>>> Paulo,
>>>>>
>>>>> I see commit with fix in master branch.
>>>>>
>>>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>>>> Author: Alexey Goncharuk <al...@gmail.com>
>>>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>>>
>>>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>>>
>>>>>
>>>>> Could you please make sure that you have codebase with this commit and
>>>>> repeat your test?
>>>>>
>>>>>
>>>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc>
>>>>> wrote:
>>>>>
>>>>>> Hi Andrey,
>>>>>>
>>>>>> This is great news! While marked as fixed, it doesn't seem to have
>>>>>> hit the Github clone repo. Am I missing something? Would like to keep on
>>>>>> testing 1.5 before it gets released.
>>>>>>
>>>>>> Pires
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Paulo,
>>>>>>>
>>>>>>> it is know issue (see JIRA ticket
>>>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>>>
>>>>>>> The problem is fixed and fix will be included into nearest
>>>>>>> ignite-1.5 release.
>>>>>>>
>>>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have the following class http://pastebin.com/QD4tmH29 and while
>>>>>>>> it works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>>>>> error is:
>>>>>>>>
>>>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>>>
>>>>>>>> Ideas?
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Pires
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Andrey Gura
>>>>>>> GridGain Systems, Inc.
>>>>>>> www.gridgain.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>> Pires
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Andrey Gura
>>>>> GridGain Systems, Inc.
>>>>> www.gridgain.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Pires
>>>>
>>>
>>>
>>
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Dmitriy Setrakyan <ds...@apache.org>.
I absolutely agree with Valentin on this. We should make sure that we
support Java serialization without any omissions. Can this be fixed quickly
before 1.5 GA is out?
D.
On Mon, Dec 7, 2015 at 11:12 AM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> Alex,
>
> I don't like this. I think both marshallers should behave in the same way
> and this behavior should be consistent with Java serialization spec. I
> hardly believe that classes like in Paulo's example will be used for
> communication with .NET/C++. And I would prefer to have such restrictions
> for interop, rather than for Java-only scenario.
>
> -Val
>
> On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
>> Paulo,
>>
>> After a closer look I see that BinaryMarshaller works the way it was
>> designed to work. The issue is that your class implements Map and
>> Serializable, but does not define writeObject(), that's why Ignite
>> serializes it in the portable format discarding information about the
>> custom user type (this way it can be read in other platforms - .NET and C++)
>>
>> There are two ways to solve this. First is to set OptimizedMarshaller in
>> configuration (this marshaller was the default marshaller in ignite-1.4).
>> The second one would be to define writeObject() method in your class which
>> will call defaultWriteObject, like this:
>>
>> private void writeObject(ObjectOutputStream s)
>> throws IOException {
>> s.defaultWriteObject();
>> }
>>
>> I am also curious what other community members think about current
>> behavior.
>>
>> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>>
>>> With 3fbf3e9 the issue is still there.
>>>
>>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>>
>>>> Paulo,
>>>>
>>>> I see commit with fix in master branch.
>>>>
>>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>>> Author: Alexey Goncharuk <al...@gmail.com>
>>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>>
>>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>>
>>>>
>>>> Could you please make sure that you have codebase with this commit and
>>>> repeat your test?
>>>>
>>>>
>>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc>
>>>> wrote:
>>>>
>>>>> Hi Andrey,
>>>>>
>>>>> This is great news! While marked as fixed, it doesn't seem to have hit
>>>>> the Github clone repo. Am I missing something? Would like to keep on
>>>>> testing 1.5 before it gets released.
>>>>>
>>>>> Pires
>>>>>
>>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Paulo,
>>>>>>
>>>>>> it is know issue (see JIRA ticket
>>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>>
>>>>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>>>>> release.
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have the following class http://pastebin.com/QD4tmH29 and while
>>>>>>> it works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>>>> error is:
>>>>>>>
>>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>>
>>>>>>> Ideas?
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Pires
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andrey Gura
>>>>>> GridGain Systems, Inc.
>>>>>> www.gridgain.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Pires
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Andrey Gura
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
While the solutions proposed are trivial to implement, I have to agree with
Valentin.
Pires
On Mon, Dec 7, 2015 at 7:12 PM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> Alex,
>
> I don't like this. I think both marshallers should behave in the same way
> and this behavior should be consistent with Java serialization spec. I
> hardly believe that classes like in Paulo's example will be used for
> communication with .NET/C++. And I would prefer to have such restrictions
> for interop, rather than for Java-only scenario.
>
> -Val
>
> On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
>> Paulo,
>>
>> After a closer look I see that BinaryMarshaller works the way it was
>> designed to work. The issue is that your class implements Map and
>> Serializable, but does not define writeObject(), that's why Ignite
>> serializes it in the portable format discarding information about the
>> custom user type (this way it can be read in other platforms - .NET and C++)
>>
>> There are two ways to solve this. First is to set OptimizedMarshaller in
>> configuration (this marshaller was the default marshaller in ignite-1.4).
>> The second one would be to define writeObject() method in your class which
>> will call defaultWriteObject, like this:
>>
>> private void writeObject(ObjectOutputStream s)
>> throws IOException {
>> s.defaultWriteObject();
>> }
>>
>> I am also curious what other community members think about current
>> behavior.
>>
>> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>>
>>> With 3fbf3e9 the issue is still there.
>>>
>>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>>
>>>> Paulo,
>>>>
>>>> I see commit with fix in master branch.
>>>>
>>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>>> Author: Alexey Goncharuk <al...@gmail.com>
>>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>>
>>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>>
>>>>
>>>> Could you please make sure that you have codebase with this commit and
>>>> repeat your test?
>>>>
>>>>
>>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc>
>>>> wrote:
>>>>
>>>>> Hi Andrey,
>>>>>
>>>>> This is great news! While marked as fixed, it doesn't seem to have hit
>>>>> the Github clone repo. Am I missing something? Would like to keep on
>>>>> testing 1.5 before it gets released.
>>>>>
>>>>> Pires
>>>>>
>>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Paulo,
>>>>>>
>>>>>> it is know issue (see JIRA ticket
>>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>>
>>>>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>>>>> release.
>>>>>>
>>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have the following class http://pastebin.com/QD4tmH29 and while
>>>>>>> it works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>>>> error is:
>>>>>>>
>>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>>
>>>>>>> Ideas?
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Pires
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andrey Gura
>>>>>> GridGain Systems, Inc.
>>>>>> www.gridgain.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Pires
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Andrey Gura
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Valentin Kulichenko <va...@gmail.com>.
Alex,
I don't like this. I think both marshallers should behave in the same way
and this behavior should be consistent with Java serialization spec. I
hardly believe that classes like in Paulo's example will be used for
communication with .NET/C++. And I would prefer to have such restrictions
for interop, rather than for Java-only scenario.
-Val
On Mon, Dec 7, 2015 at 9:51 AM, Alexey Goncharuk <alexey.goncharuk@gmail.com
> wrote:
> Paulo,
>
> After a closer look I see that BinaryMarshaller works the way it was
> designed to work. The issue is that your class implements Map and
> Serializable, but does not define writeObject(), that's why Ignite
> serializes it in the portable format discarding information about the
> custom user type (this way it can be read in other platforms - .NET and C++)
>
> There are two ways to solve this. First is to set OptimizedMarshaller in
> configuration (this marshaller was the default marshaller in ignite-1.4).
> The second one would be to define writeObject() method in your class which
> will call defaultWriteObject, like this:
>
> private void writeObject(ObjectOutputStream s)
> throws IOException {
> s.defaultWriteObject();
> }
>
> I am also curious what other community members think about current
> behavior.
>
> 2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
>
>> With 3fbf3e9 the issue is still there.
>>
>> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>
>>> Paulo,
>>>
>>> I see commit with fix in master branch.
>>>
>>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>>> Author: Alexey Goncharuk <al...@gmail.com>
>>> Date: Tue Dec 1 17:37:41 2015 +0300
>>>
>>> IGNITE-1695 - Fixed writing polymorphic types.
>>>
>>>
>>> Could you please make sure that you have codebase with this commit and
>>> repeat your test?
>>>
>>>
>>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>>>
>>>> Hi Andrey,
>>>>
>>>> This is great news! While marked as fixed, it doesn't seem to have hit
>>>> the Github clone repo. Am I missing something? Would like to keep on
>>>> testing 1.5 before it gets released.
>>>>
>>>> Pires
>>>>
>>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com>
>>>> wrote:
>>>>
>>>>> Hi Paulo,
>>>>>
>>>>> it is know issue (see JIRA ticket
>>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>>
>>>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>>>> release.
>>>>>
>>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>>>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>>> error is:
>>>>>>
>>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>>
>>>>>> Ideas?
>>>>>> --
>>>>>> Cheers,
>>>>>> Pires
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Andrey Gura
>>>>> GridGain Systems, Inc.
>>>>> www.gridgain.com
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Pires
>>>>
>>>
>>>
>>>
>>> --
>>> Andrey Gura
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Alexey Goncharuk <al...@gmail.com>.
Paulo,
After a closer look I see that BinaryMarshaller works the way it was
designed to work. The issue is that your class implements Map and
Serializable, but does not define writeObject(), that's why Ignite
serializes it in the portable format discarding information about the
custom user type (this way it can be read in other platforms - .NET and C++)
There are two ways to solve this. First is to set OptimizedMarshaller in
configuration (this marshaller was the default marshaller in ignite-1.4).
The second one would be to define writeObject() method in your class which
will call defaultWriteObject, like this:
private void writeObject(ObjectOutputStream s)
throws IOException {
s.defaultWriteObject();
}
I am also curious what other community members think about current behavior.
2015-12-07 20:38 GMT+03:00 Paulo Pires <pi...@littlebits.cc>:
> With 3fbf3e9 the issue is still there.
>
> On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com> wrote:
>
>> Paulo,
>>
>> I see commit with fix in master branch.
>>
>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>> Author: Alexey Goncharuk <al...@gmail.com>
>> Date: Tue Dec 1 17:37:41 2015 +0300
>>
>> IGNITE-1695 - Fixed writing polymorphic types.
>>
>>
>> Could you please make sure that you have codebase with this commit and
>> repeat your test?
>>
>>
>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>>
>>> Hi Andrey,
>>>
>>> This is great news! While marked as fixed, it doesn't seem to have hit
>>> the Github clone repo. Am I missing something? Would like to keep on
>>> testing 1.5 before it gets released.
>>>
>>> Pires
>>>
>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>>
>>>> Hi Paulo,
>>>>
>>>> it is know issue (see JIRA ticket
>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>
>>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>>> release.
>>>>
>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>> error is:
>>>>>
>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>
>>>>> Ideas?
>>>>> --
>>>>> Cheers,
>>>>> Pires
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Andrey Gura
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>>
>> --
>> Andrey Gura
>> GridGain Systems, Inc.
>> www.gridgain.com
>>
>
>
>
> --
> Cheers,
> Pires
>
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
With 3fbf3e9 the issue is still there.
On Mon, Dec 7, 2015 at 11:28 AM, Andrey Gura <ag...@gridgain.com> wrote:
> Paulo,
>
> I see commit with fix in master branch.
>
> commit 2564a556e353269d4adc58160512ed9d0a5979b4
> Author: Alexey Goncharuk <al...@gmail.com>
> Date: Tue Dec 1 17:37:41 2015 +0300
>
> IGNITE-1695 - Fixed writing polymorphic types.
>
>
> Could you please make sure that you have codebase with this commit and
> repeat your test?
>
>
> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> Hi Andrey,
>>
>> This is great news! While marked as fixed, it doesn't seem to have hit
>> the Github clone repo. Am I missing something? Would like to keep on
>> testing 1.5 before it gets released.
>>
>> Pires
>>
>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>
>>> Hi Paulo,
>>>
>>> it is know issue (see JIRA ticket
>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>
>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>> release.
>>>
>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>> error is:
>>>>
>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>> xxx.DeviceSubscriptionFilterMap
>>>>
>>>> Ideas?
>>>> --
>>>> Cheers,
>>>> Pires
>>>>
>>>
>>>
>>>
>>> --
>>> Andrey Gura
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Andrey Gura <ag...@gridgain.com>.
Paulo,
I see commit with fix in master branch.
commit 2564a556e353269d4adc58160512ed9d0a5979b4
Author: Alexey Goncharuk <al...@gmail.com>
Date: Tue Dec 1 17:37:41 2015 +0300
IGNITE-1695 - Fixed writing polymorphic types.
Could you please make sure that you have codebase with this commit and
repeat your test?
On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
> Hi Andrey,
>
> This is great news! While marked as fixed, it doesn't seem to have hit the
> Github clone repo. Am I missing something? Would like to keep on testing
> 1.5 before it gets released.
>
> Pires
>
> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>
>> Hi Paulo,
>>
>> it is know issue (see JIRA ticket
>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>
>> The problem is fixed and fix will be included into nearest ignite-1.5
>> release.
>>
>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>>
>>> Hi,
>>>
>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>> error is:
>>>
>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>> xxx.DeviceSubscriptionFilterMap
>>>
>>> Ideas?
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>>
>> --
>> Andrey Gura
>> GridGain Systems, Inc.
>> www.gridgain.com
>>
>
>
>
> --
> Cheers,
> Pires
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
It seems to have been merged in the meanwhile. Going to try and report back!
On Mon, Dec 7, 2015 at 11:31 AM, Paulo Pires <pi...@littlebits.cc> wrote:
> I cloned the Github repo ~16 hours ago and the latest commit is 357d791
>
> Pires
>
> On Mon, Dec 7, 2015 at 11:12 AM, Andrey Gura <ag...@gridgain.com> wrote:
>
>> Paulo,
>>
>> I see commit with fix in master branch.
>>
>> commit 2564a556e353269d4adc58160512ed9d0a5979b4
>> Author: Alexey Goncharuk <al...@gmail.com>
>> Date: Tue Dec 1 17:37:41 2015 +0300
>>
>> IGNITE-1695 - Fixed writing polymorphic types.
>>
>>
>> Could you please make sure that you have codebase with this commit and
>> repeat your test?
>>
>>
>> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>>
>>> Hi Andrey,
>>>
>>> This is great news! While marked as fixed, it doesn't seem to have hit
>>> the Github clone repo. Am I missing something? Would like to keep on
>>> testing 1.5 before it gets released.
>>>
>>> Pires
>>>
>>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>>
>>>> Hi Paulo,
>>>>
>>>> it is know issue (see JIRA ticket
>>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>>
>>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>>> release.
>>>>
>>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>>> error is:
>>>>>
>>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>>> xxx.DeviceSubscriptionFilterMap
>>>>>
>>>>> Ideas?
>>>>> --
>>>>> Cheers,
>>>>> Pires
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Andrey Gura
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>>
>> --
>> Andrey Gura
>> GridGain Systems, Inc.
>> www.gridgain.com
>>
>
>
>
> --
> Cheers,
> Pires
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
I cloned the Github repo ~16 hours ago and the latest commit is 357d791
Pires
On Mon, Dec 7, 2015 at 11:12 AM, Andrey Gura <ag...@gridgain.com> wrote:
> Paulo,
>
> I see commit with fix in master branch.
>
> commit 2564a556e353269d4adc58160512ed9d0a5979b4
> Author: Alexey Goncharuk <al...@gmail.com>
> Date: Tue Dec 1 17:37:41 2015 +0300
>
> IGNITE-1695 - Fixed writing polymorphic types.
>
>
> Could you please make sure that you have codebase with this commit and
> repeat your test?
>
>
> On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> Hi Andrey,
>>
>> This is great news! While marked as fixed, it doesn't seem to have hit
>> the Github clone repo. Am I missing something? Would like to keep on
>> testing 1.5 before it gets released.
>>
>> Pires
>>
>> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>>
>>> Hi Paulo,
>>>
>>> it is know issue (see JIRA ticket
>>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>>
>>> The problem is fixed and fix will be included into nearest ignite-1.5
>>> release.
>>>
>>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>>> error is:
>>>>
>>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>>> xxx.DeviceSubscriptionFilterMap
>>>>
>>>> Ideas?
>>>> --
>>>> Cheers,
>>>> Pires
>>>>
>>>
>>>
>>>
>>> --
>>> Andrey Gura
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>>
>>
>>
>> --
>> Cheers,
>> Pires
>>
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Andrey Gura <ag...@gridgain.com>.
Paulo,
I see commit with fix in master branch.
commit 2564a556e353269d4adc58160512ed9d0a5979b4
Author: Alexey Goncharuk <al...@gmail.com>
Date: Tue Dec 1 17:37:41 2015 +0300
IGNITE-1695 - Fixed writing polymorphic types.
Could you please make sure that you have codebase with this commit and
repeat your test?
On Mon, Dec 7, 2015 at 1:37 PM, Paulo Pires <pi...@littlebits.cc> wrote:
> Hi Andrey,
>
> This is great news! While marked as fixed, it doesn't seem to have hit the
> Github clone repo. Am I missing something? Would like to keep on testing
> 1.5 before it gets released.
>
> Pires
>
> On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
>
>> Hi Paulo,
>>
>> it is know issue (see JIRA ticket
>> https://issues.apache.org/jira/browse/IGNITE-1695)
>>
>> The problem is fixed and fix will be included into nearest ignite-1.5
>> release.
>>
>> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>>
>>> Hi,
>>>
>>> I have the following class http://pastebin.com/QD4tmH29 and while it
>>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>>> error is:
>>>
>>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>>> xxx.DeviceSubscriptionFilterMap
>>>
>>> Ideas?
>>> --
>>> Cheers,
>>> Pires
>>>
>>
>>
>>
>> --
>> Andrey Gura
>> GridGain Systems, Inc.
>> www.gridgain.com
>>
>
>
>
> --
> Cheers,
> Pires
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Paulo Pires <pi...@littlebits.cc>.
Hi Andrey,
This is great news! While marked as fixed, it doesn't seem to have hit the
Github clone repo. Am I missing something? Would like to keep on testing
1.5 before it gets released.
Pires
On Mon, Dec 7, 2015 at 10:22 AM, Andrey Gura <ag...@gridgain.com> wrote:
> Hi Paulo,
>
> it is know issue (see JIRA ticket
> https://issues.apache.org/jira/browse/IGNITE-1695)
>
> The problem is fixed and fix will be included into nearest ignite-1.5
> release.
>
> On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
>
>> Hi,
>>
>> I have the following class http://pastebin.com/QD4tmH29 and while it
>> works fine with 1.4.0 it is not working with 1.5 built from source. The
>> error is:
>>
>> java.lang.ClassCastException: java.util.HashMap cannot be cast to
>> xxx.DeviceSubscriptionFilterMap
>>
>> Ideas?
>> --
>> Cheers,
>> Pires
>>
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>
--
Cheers,
Pires
Re: Serialization issue with Ignite 1.5 built from master (357d791)
Posted by Andrey Gura <ag...@gridgain.com>.
Hi Paulo,
it is know issue (see JIRA ticket
https://issues.apache.org/jira/browse/IGNITE-1695)
The problem is fixed and fix will be included into nearest ignite-1.5
release.
On Mon, Dec 7, 2015 at 2:32 AM, Paulo Pires <pi...@littlebits.cc> wrote:
> Hi,
>
> I have the following class http://pastebin.com/QD4tmH29 and while it
> works fine with 1.4.0 it is not working with 1.5 built from source. The
> error is:
>
> java.lang.ClassCastException: java.util.HashMap cannot be cast to
> xxx.DeviceSubscriptionFilterMap
>
> Ideas?
> --
> Cheers,
> Pires
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com