1.5.final

[dsetrakyan]

I would like to assemble a list of the remaining issues for the 1.5 final
release. Can everyone in the community please reply here with a list of
tickets you are still working on for 1.5 release?

Thanks,
D.

[Alexey Goncharuk]

Status for the opened tickets from my side:

https://issues.apache.org/jira/browse/IGNITE-2078The original issue
reported has been fixed. Now sometimes the example returns duplicate
records for TXT queries, this is related to changing topology not being
handled in TXT queries. This is an old issue and it is not critical for the
release

 IGNITE-2190 - Reported by Denis. Added test, fixed and merged to igntie-1.5

The only issue that I had not time to take a look at is
https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers multiple
deserializations of cache value. There is no a simple fix for this, however
I see that the fix version for this ticket is 1.6. Can somebody confirm
that it is not critical for the release?
On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]> wrote:

> I would like to assemble a list of the remaining issues for the 1.5 final
> release. Can everyone in the community please reply here with a list of
> tickets you are still working on for 1.5 release?
>
> Thanks,
> D.
>

[dsetrakyan]

Alexey,

About IGNITE-2212 - can you explain why the value is deserialized at all,
even once, let alone multiple times?

D.

On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
[hidden email]> wrote:

> Status for the opened tickets from my side:
>
> https://issues.apache.org/jira/browse/IGNITE-2078The original issue
> reported has been fixed. Now sometimes the example returns duplicate
> records for TXT queries, this is related to changing topology not being
> handled in TXT queries. This is an old issue and it is not critical for the
> release
>
>  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
> igntie-1.5
>
> The only issue that I had not time to take a look at is
> https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
> multiple
> deserializations of cache value. There is no a simple fix for this, however
> I see that the fix version for this ticket is 1.6. Can somebody confirm
> that it is not critical for the release?
> On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]> wrote:
>
> > I would like to assemble a list of the remaining issues for the 1.5 final
> > release. Can everyone in the community please reply here with a list of
> > tickets you are still working on for 1.5 release?
> >
> > Thanks,
> > D.
> >
>

[Valentin Kulichenko]

Regarding IGNITE-2212. The original issue is reproduced only with optimized
marshaller, so I don't think it's critical. But at the same time I observe
strange behavior when I run the same test with binary marshaller: to send
an Externalizable object across network, we serialize, deserialize, and
then serialize it again, all on client side :)

I believe that's because our latest changes for Externalizables -
CacheObjectBinaryProcessorImpl.marshalToBinary() method doesn't properly
handle them. Actually, I don't think we should call it in this case at all.
Alexey, can you take a look? I think this one should be fixed in 1.5.

-Val

On Mon, Dec 21, 2015 at 9:17 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Alexey,
>
> About IGNITE-2212 - can you explain why the value is deserialized at all,
> even once, let alone multiple times?
>
> D.
>
> On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
> [hidden email]> wrote:
>
> > Status for the opened tickets from my side:
> >
> > https://issues.apache.org/jira/browse/IGNITE-2078The original issue
> > reported has been fixed. Now sometimes the example returns duplicate
> > records for TXT queries, this is related to changing topology not being
> > handled in TXT queries. This is an old issue and it is not critical for
> the
> > release
> >
> >  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
> > igntie-1.5
> >
> > The only issue that I had not time to take a look at is
> > https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
> > multiple
> > deserializations of cache value. There is no a simple fix for this,
> however
> > I see that the fix version for this ticket is 1.6. Can somebody confirm
> > that it is not critical for the release?
> > On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]>
> wrote:
> >
> > > I would like to assemble a list of the remaining issues for the 1.5
> final
> > > release. Can everyone in the community please reply here with a list of
> > > tickets you are still working on for 1.5 release?
> > >
> > > Thanks,
> > > D.
> > >
> >
>

[dsetrakyan]

Valentin, great catch! You should add this test to the cache suite and make
sure it fails, so we will be certain to fix it before the final release.
Let’s also file a blocker ticket for it.

Moreover, we should have an identical test for non-externalizable classes,
however I am not sure yet how to count the number of (de)serializations in
that case. Any ideas?

D.

On Mon, Dec 21, 2015 at 5:31 PM, Valentin Kulichenko <
[hidden email]> wrote:

> Regarding IGNITE-2212. The original issue is reproduced only with optimized
> marshaller, so I don't think it's critical. But at the same time I observe
> strange behavior when I run the same test with binary marshaller: to send
> an Externalizable object across network, we serialize, deserialize, and
> then serialize it again, all on client side :)
>
> I believe that's because our latest changes for Externalizables -
> CacheObjectBinaryProcessorImpl.marshalToBinary() method doesn't properly
> handle them. Actually, I don't think we should call it in this case at all.
> Alexey, can you take a look? I think this one should be fixed in 1.5.
>
> -Val
>
> On Mon, Dec 21, 2015 at 9:17 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Alexey,
> >
> > About IGNITE-2212 - can you explain why the value is deserialized at all,
> > even once, let alone multiple times?
> >
> > D.
> >
> > On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
> > [hidden email]> wrote:
> >
> > > Status for the opened tickets from my side:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-2078The original issue
> > > reported has been fixed. Now sometimes the example returns duplicate
> > > records for TXT queries, this is related to changing topology not being
> > > handled in TXT queries. This is an old issue and it is not critical for
> > the
> > > release
> > >
> > >  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
> > > igntie-1.5
> > >
> > > The only issue that I had not time to take a look at is
> > > https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
> > > multiple
> > > deserializations of cache value. There is no a simple fix for this,
> > however
> > > I see that the fix version for this ticket is 1.6. Can somebody confirm
> > > that it is not critical for the release?
> > > On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]>
> > wrote:
> > >
> > > > I would like to assemble a list of the remaining issues for the 1.5
> > final
> > > > release. Can everyone in the community please reply here with a list
> of
> > > > tickets you are still working on for 1.5 release?
> > > >
> > > > Thanks,
> > > > D.
> > > >
> > >
> >
>

[Vladimir Ozerov]

As per my I tickets, I have only single task targeting 1.5 -
https://issues.apache.org/jira/browse/IGNITE-2209 Hope it will be finished
in the nearest time.

As per Externalizable issue, this could be due to my latests changes to
serialization logic. For now both Externalizables and objects with
writeObject/readObject methods are treated in the same way - they are
serialized using OptimizedMarshalling. This could be possible reason of
observed deserializations, but we need to double-check that.

On Tue, Dec 22, 2015 at 4:34 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Valentin, great catch! You should add this test to the cache suite and make
> sure it fails, so we will be certain to fix it before the final release.
> Let’s also file a blocker ticket for it.
>
> Moreover, we should have an identical test for non-externalizable classes,
> however I am not sure yet how to count the number of (de)serializations in
> that case. Any ideas?
>
> D.
>
> On Mon, Dec 21, 2015 at 5:31 PM, Valentin Kulichenko <
> [hidden email]> wrote:
>
> > Regarding IGNITE-2212. The original issue is reproduced only with
> optimized
> > marshaller, so I don't think it's critical. But at the same time I
> observe
> > strange behavior when I run the same test with binary marshaller: to send
> > an Externalizable object across network, we serialize, deserialize, and
> > then serialize it again, all on client side :)
> >
> > I believe that's because our latest changes for Externalizables -
> > CacheObjectBinaryProcessorImpl.marshalToBinary() method doesn't properly
> > handle them. Actually, I don't think we should call it in this case at
> all.
> > Alexey, can you take a look? I think this one should be fixed in 1.5.
> >
> > -Val
> >
> > On Mon, Dec 21, 2015 at 9:17 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> > > Alexey,
> > >
> > > About IGNITE-2212 - can you explain why the value is deserialized at
> all,
> > > even once, let alone multiple times?
> > >
> > > D.
> > >
> > > On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
> > > [hidden email]> wrote:
> > >
> > > > Status for the opened tickets from my side:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-2078The original issue
> > > > reported has been fixed. Now sometimes the example returns duplicate
> > > > records for TXT queries, this is related to changing topology not
> being
> > > > handled in TXT queries. This is an old issue and it is not critical
> for
> > > the
> > > > release
> > > >
> > > >  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
> > > > igntie-1.5
> > > >
> > > > The only issue that I had not time to take a look at is
> > > > https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
> > > > multiple
> > > > deserializations of cache value. There is no a simple fix for this,
> > > however
> > > > I see that the fix version for this ticket is 1.6. Can somebody
> confirm
> > > > that it is not critical for the release?
> > > > On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]>
> > > wrote:
> > > >
> > > > > I would like to assemble a list of the remaining issues for the 1.5
> > > final
> > > > > release. Can everyone in the community please reply here with a
> list
> > of
> > > > > tickets you are still working on for 1.5 release?
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > >
> > >
> >
>

[Valentin Kulichenko]

Here is the ticket for this issue:
https://issues.apache.org/jira/browse/IGNITE-2225

On Mon, Dec 21, 2015 at 10:00 PM, Vladimir Ozerov <[hidden email]>
wrote:

> As per my I tickets, I have only single task targeting 1.5 -
> https://issues.apache.org/jira/browse/IGNITE-2209 Hope it will be finished
> in the nearest time.
>
> As per Externalizable issue, this could be due to my latests changes to
> serialization logic. For now both Externalizables and objects with
> writeObject/readObject methods are treated in the same way - they are
> serialized using OptimizedMarshalling. This could be possible reason of
> observed deserializations, but we need to double-check that.
>
> On Tue, Dec 22, 2015 at 4:34 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Valentin, great catch! You should add this test to the cache suite and
> make
> > sure it fails, so we will be certain to fix it before the final release.
> > Let’s also file a blocker ticket for it.
> >
> > Moreover, we should have an identical test for non-externalizable
> classes,
> > however I am not sure yet how to count the number of (de)serializations
> in
> > that case. Any ideas?
> >
> > D.
> >
> > On Mon, Dec 21, 2015 at 5:31 PM, Valentin Kulichenko <
> > [hidden email]> wrote:
> >
> > > Regarding IGNITE-2212. The original issue is reproduced only with
> > optimized
> > > marshaller, so I don't think it's critical. But at the same time I
> > observe
> > > strange behavior when I run the same test with binary marshaller: to
> send
> > > an Externalizable object across network, we serialize, deserialize, and
> > > then serialize it again, all on client side :)
> > >
> > > I believe that's because our latest changes for Externalizables -
> > > CacheObjectBinaryProcessorImpl.marshalToBinary() method doesn't
> properly
> > > handle them. Actually, I don't think we should call it in this case at
> > all.
> > > Alexey, can you take a look? I think this one should be fixed in 1.5.
> > >
> > > -Val
> > >
> > > On Mon, Dec 21, 2015 at 9:17 AM, Dmitriy Setrakyan <
> > [hidden email]>
> > > wrote:
> > >
> > > > Alexey,
> > > >
> > > > About IGNITE-2212 - can you explain why the value is deserialized at
> > all,
> > > > even once, let alone multiple times?
> > > >
> > > > D.
> > > >
> > > > On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
> > > > [hidden email]> wrote:
> > > >
> > > > > Status for the opened tickets from my side:
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-2078The original
> issue
> > > > > reported has been fixed. Now sometimes the example returns
> duplicate
> > > > > records for TXT queries, this is related to changing topology not
> > being
> > > > > handled in TXT queries. This is an old issue and it is not critical
> > for
> > > > the
> > > > > release
> > > > >
> > > > >  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
> > > > > igntie-1.5
> > > > >
> > > > > The only issue that I had not time to take a look at is
> > > > > https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
> > > > > multiple
> > > > > deserializations of cache value. There is no a simple fix for this,
> > > > however
> > > > > I see that the fix version for this ticket is 1.6. Can somebody
> > confirm
> > > > > that it is not critical for the release?
> > > > > On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]>
> > > > wrote:
> > > > >
> > > > > > I would like to assemble a list of the remaining issues for the
> 1.5
> > > > final
> > > > > > release. Can everyone in the community please reply here with a
> > list
> > > of
> > > > > > tickets you are still working on for 1.5 release?
> > > > > >
> > > > > > Thanks,
> > > > > > D.
> > > > > >
> > > > >
> > > >
> > >
> >
>

[Vladimir Ozerov]

Sorry, I meant *IGNITE-2213*, not IGNITE-2209.

On Tue, Dec 22, 2015 at 9:00 AM, Vladimir Ozerov <[hidden email]>
wrote:

> As per my I tickets, I have only single task targeting 1.5 -
> https://issues.apache.org/jira/browse/IGNITE-2209 Hope it will be
> finished in the nearest time.
>
> As per Externalizable issue, this could be due to my latests changes to
> serialization logic. For now both Externalizables and objects with
> writeObject/readObject methods are treated in the same way - they are
> serialized using OptimizedMarshalling. This could be possible reason of
> observed deserializations, but we need to double-check that.
>
> On Tue, Dec 22, 2015 at 4:34 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
>> Valentin, great catch! You should add this test to the cache suite and
>> make
>> sure it fails, so we will be certain to fix it before the final release.
>> Let’s also file a blocker ticket for it.
>>
>> Moreover, we should have an identical test for non-externalizable classes,
>> however I am not sure yet how to count the number of (de)serializations in
>> that case. Any ideas?
>>
>> D.
>>
>> On Mon, Dec 21, 2015 at 5:31 PM, Valentin Kulichenko <
>> [hidden email]> wrote:
>>
>> > Regarding IGNITE-2212. The original issue is reproduced only with
>> optimized
>> > marshaller, so I don't think it's critical. But at the same time I
>> observe
>> > strange behavior when I run the same test with binary marshaller: to
>> send
>> > an Externalizable object across network, we serialize, deserialize, and
>> > then serialize it again, all on client side :)
>> >
>> > I believe that's because our latest changes for Externalizables -
>> > CacheObjectBinaryProcessorImpl.marshalToBinary() method doesn't properly
>> > handle them. Actually, I don't think we should call it in this case at
>> all.
>> > Alexey, can you take a look? I think this one should be fixed in 1.5.
>> >
>> > -Val
>> >
>> > On Mon, Dec 21, 2015 at 9:17 AM, Dmitriy Setrakyan <
>> [hidden email]>
>> > wrote:
>> >
>> > > Alexey,
>> > >
>> > > About IGNITE-2212 - can you explain why the value is deserialized at
>> all,
>> > > even once, let alone multiple times?
>> > >
>> > > D.
>> > >
>> > > On Mon, Dec 21, 2015 at 8:57 AM, Alexey Goncharuk <
>> > > [hidden email]> wrote:
>> > >
>> > > > Status for the opened tickets from my side:
>> > > >
>> > > > https://issues.apache.org/jira/browse/IGNITE-2078The original issue
>> > > > reported has been fixed. Now sometimes the example returns duplicate
>> > > > records for TXT queries, this is related to changing topology not
>> being
>> > > > handled in TXT queries. This is an old issue and it is not critical
>> for
>> > > the
>> > > > release
>> > > >
>> > > >  IGNITE-2190 - Reported by Denis. Added test, fixed and merged to
>> > > > igntie-1.5
>> > > >
>> > > > The only issue that I had not time to take a look at is
>> > > > https://issues.apache.org/jira/browse/IGNITE-2212- tx put triggers
>> > > > multiple
>> > > > deserializations of cache value. There is no a simple fix for this,
>> > > however
>> > > > I see that the fix version for this ticket is 1.6. Can somebody
>> confirm
>> > > > that it is not critical for the release?
>> > > > On Dec 21, 2015 19:34, "Dmitriy Setrakyan" <[hidden email]>
>> > > wrote:
>> > > >
>> > > > > I would like to assemble a list of the remaining issues for the
>> 1.5
>> > > final
>> > > > > release. Can everyone in the community please reply here with a
>> list
>> > of
>> > > > > tickets you are still working on for 1.5 release?
>> > > > >
>> > > > > Thanks,
>> > > > > D.
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

[Konstantin Boudnik-2]

1.5.final is bigger that 1.5.0-b1? Or lesser?

On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> I would like to assemble a list of the remaining issues for the 1.5 final
> release. Can everyone in the community please reply here with a list of
> tickets you are still working on for 1.5 release?
>
> Thanks,
> D.

[dsetrakyan]

From maven standpoint, 1.5.0.final comes after 1.5.0-b1. Can someone double
confirm this?

D.

On Mon, Dec 21, 2015 at 10:34 PM, Konstantin Boudnik <[hidden email]> wrote:

> 1.5.final is bigger that 1.5.0-b1? Or lesser?
>
> On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > I would like to assemble a list of the remaining issues for the 1.5 final
> > release. Can everyone in the community please reply here with a list of
> > tickets you are still working on for 1.5 release?
> >
> > Thanks,
> > D.
>

[Anton Vinogradov]

My tickets:

IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final

IGNITE-2175 Not valid exceptions in case when example can't works with
remote node started with server classpath (Java 7)

Both should be ready today.

IGNITE-2116 ignite-osgi-karaf has only readme and license files
Waiting for Raul's answer.

On Tue, Dec 22, 2015 at 10:45 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> From maven standpoint, 1.5.0.final comes after 1.5.0-b1. Can someone double
> confirm this?
>
> D.
>
> On Mon, Dec 21, 2015 at 10:34 PM, Konstantin Boudnik <[hidden email]>
> wrote:
>
> > 1.5.final is bigger that 1.5.0-b1? Or lesser?
> >
> > On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > > I would like to assemble a list of the remaining issues for the 1.5
> final
> > > release. Can everyone in the community please reply here with a list of
> > > tickets you are still working on for 1.5 release?
> > >
> > > Thanks,
> > > D.
> >
>

[dsetrakyan]

Anton,

I think it is worth while to send your question for IGNITE-2116 here as
well. Perhaps Raul will have access to the email and respond.

D.

On Tue, Dec 22, 2015 at 1:25 AM, Anton Vinogradov <[hidden email]>
wrote:

> My tickets:
>
> IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final
>
> IGNITE-2175 Not valid exceptions in case when example can't works with
> remote node started with server classpath (Java 7)
>
> Both should be ready today.
>
> IGNITE-2116 ignite-osgi-karaf has only readme and license files
> Waiting for Raul's answer.
>
> On Tue, Dec 22, 2015 at 10:45 AM, Dmitriy Setrakyan <[hidden email]
> >
> wrote:
>
> > From maven standpoint, 1.5.0.final comes after 1.5.0-b1. Can someone
> double
> > confirm this?
> >
> > D.
> >
> > On Mon, Dec 21, 2015 at 10:34 PM, Konstantin Boudnik <[hidden email]>
> > wrote:
> >
> > > 1.5.final is bigger that 1.5.0-b1? Or lesser?
> > >
> > > On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > > > I would like to assemble a list of the remaining issues for the 1.5
> > final
> > > > release. Can everyone in the community please reply here with a list
> of
> > > > tickets you are still working on for 1.5 release?
> > > >
> > > > Thanks,
> > > > D.
> > >
> >
>

[Sergey Kozlov]

We found yet another blocker issue (the behavior changed it becomes more
important from my standpoint):

IGNITE-2200 CacheQueryExample failes after CacheClientBinaryQueryExample
and vice versa <https://issues.apache.org/jira/browse/IGNITE-2200>

Alexey could you take a look and investigate it? If not please let us know

On Tue, Dec 22, 2015 at 12:41 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Anton,
>
> I think it is worth while to send your question for IGNITE-2116 here as
> well. Perhaps Raul will have access to the email and respond.
>
> D.
>
> On Tue, Dec 22, 2015 at 1:25 AM, Anton Vinogradov <
> [hidden email]>
> wrote:
>
> > My tickets:
> >
> > IGNITE-2226 Replace dash in 1.5.0-final with dot 1.5.0.final
> >
> > IGNITE-2175 Not valid exceptions in case when example can't works with
> > remote node started with server classpath (Java 7)
> >
> > Both should be ready today.
> >
> > IGNITE-2116 ignite-osgi-karaf has only readme and license files
> > Waiting for Raul's answer.
> >
> > On Tue, Dec 22, 2015 at 10:45 AM, Dmitriy Setrakyan <
> [hidden email]
> > >
> > wrote:
> >
> > > From maven standpoint, 1.5.0.final comes after 1.5.0-b1. Can someone
> > double
> > > confirm this?
> > >
> > > D.
> > >
> > > On Mon, Dec 21, 2015 at 10:34 PM, Konstantin Boudnik <[hidden email]>
> > > wrote:
> > >
> > > > 1.5.final is bigger that 1.5.0-b1? Or lesser?
> > > >
> > > > On Mon, Dec 21, 2015 at 08:33AM, Dmitriy Setrakyan wrote:
> > > > > I would like to assemble a list of the remaining issues for the 1.5
> > > final
> > > > > release. Can everyone in the community please reply here with a
> list
> > of
> > > > > tickets you are still working on for 1.5 release?
> > > > >
> > > > > Thanks,
> > > > > D.
> > > >
> > >
> >
>

--
Sergey Kozlov

[Alexey Goncharuk]

​Sure, I will provide my feedback in a couple of hours.

[Raul Kripalani]

On Tue, Dec 22, 2015 at 9:25 AM, Anton Vinogradov <[hidden email]>
wrote:

> IGNITE-2116 ignite-osgi-karaf has only readme and license files
> Waiting for Raul's answer.
>

Replied in the ticket. Sorry for the delay. Too many open fronts!

*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

[Alexey Goncharuk]

Looks like it is a duplicate of IGNITE-2135.
The issue is caused by not setting deployment info bean in query request
when binary marshaller is used.

I anticipate the fix to be pretty simple, though need some more time to add
a proper test and to run CI. Will send an update once all is done.

[dsetrakyan]

As of today, there are still 4 tickets open:
http://s.apache.org/ignite-1.5.0.final

Anton - 2 tickets
Vladimir - 1 ticket
Alexey - 1 ticket

D.


On Tue, Dec 22, 2015 at 5:50 AM, Alexey Goncharuk <
[hidden email]> wrote:

> Looks like it is a duplicate of IGNITE-2135.
> The issue is caused by not setting deployment info bean in query request
> when binary marshaller is used.
>
> I anticipate the fix to be pretty simple, though need some more time to add
> a proper test and to run CI. Will send an update once all is done.
>

[Vladimir Ozerov]

I closed my ticket. There was a problem in test preventing compilation with
Java 8.

On Wed, Dec 23, 2015 at 4:54 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> As of today, there are still 4 tickets open:
> http://s.apache.org/ignite-1.5.0.final
>
> Anton - 2 tickets
> Vladimir - 1 ticket
> Alexey - 1 ticket
>
> D.
>
>
> On Tue, Dec 22, 2015 at 5:50 AM, Alexey Goncharuk <
> [hidden email]> wrote:
>
> > Looks like it is a duplicate of IGNITE-2135.
> > The issue is caused by not setting deployment info bean in query request
> > when binary marshaller is used.
> >
> > I anticipate the fix to be pretty simple, though need some more time to
> add
> > a proper test and to run CI. Will send an update once all is done.
> >
>

[Anton Vinogradov]

I closed one,
Left:  IGNITE-2175 Not valid exceptions in case when example can't works
with remote node started with server classpath (Java 7)

On Wed, Dec 23, 2015 at 9:22 AM, Vladimir Ozerov <[hidden email]>
wrote:

> I closed my ticket. There was a problem in test preventing compilation with
> Java 8.
>
> On Wed, Dec 23, 2015 at 4:54 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > As of today, there are still 4 tickets open:
> > http://s.apache.org/ignite-1.5.0.final
> >
> > Anton - 2 tickets
> > Vladimir - 1 ticket
> > Alexey - 1 ticket
> >
> > D.
> >
> >
> > On Tue, Dec 22, 2015 at 5:50 AM, Alexey Goncharuk <
> > [hidden email]> wrote:
> >
> > > Looks like it is a duplicate of IGNITE-2135.
> > > The issue is caused by not setting deployment info bean in query
> request
> > > when binary marshaller is used.
> > >
> > > I anticipate the fix to be pretty simple, though need some more time to
> > add
> > > a proper test and to run CI. Will send an update once all is done.
> > >
> >
>

[Alexey Goncharuk]

The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been
merged to ignite-1.5​