Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > Thank you Alexey. > > Any ETA

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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)

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 wrote: > Paulo, > > We probably

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > Hi Alexey, > > Is there any workaround I can use to circumvent

Re: Serialization issue with Ignite 1.5 built from master (357d791)

Alexey, Do you mean this? class MyWrapper { // Wrapped map. Map<> myMap = …; } D. On Tue, Jan 12, 2016 at 10:25 AM, Alexey Goncharuk < alexey.goncha...@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

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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.goncha...@gmail.com> wrote: > Thanks Paulo, > > I've reproduced the

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > 1.5.0.final doesn't fix this. Is there a way I can use 1.5.0.final? > >

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > I absolutely agree with Valentin on this. We should make sure that we > support Java serialization without any omissions. Can this be fixed

Re: Serialization issue with Ignite 1.5 built from master (357d791)

OptimizedMarshaller doesn't work as well. igniteConfig.setMarshaller(new OptimizedMarshaller()); On Mon, Jan 11, 2016 at 12:59 PM, Paulo Pires wrote: > The following does not work. > > private void writeObject(ObjectOutputStream s) > throws IOException { >

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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)

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!

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > Hi, > > I have the following class

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > Hi Paulo, > > it is know

Re: Serialization issue with Ignite 1.5 built from master (357d791)

Paulo, I see commit with fix in master branch. commit 2564a556e353269d4adc58160512ed9d0a5979b4 Author: Alexey Goncharuk 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

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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 wrote: > Paulo, > > I see commit with fix in master branch. > > commit 2564a556e353269d4adc58160512ed9d0a5979b4 > Author: Alexey Goncharuk

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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

Re: Serialization issue with Ignite 1.5 built from master (357d791)

Paulo, I see commit with fix in master branch. commit 2564a556e353269d4adc58160512ed9d0a5979b4 Author: Alexey Goncharuk 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

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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.kuliche...@gmail.com> wrote: > Alex, > > I don't like this. I think both marshallers should behave in the same way > and this behavior

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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.kuliche...@gmail.com> wrote: > Alex, > > I don't like this.

Re: Serialization issue with Ignite 1.5 built from master (357d791)

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