Re: 1.5.final

[Dmitriy Setrakyan]

On Thu, Dec 24, 2015 at 11:23 PM, Sergey Kozlov 
wrote:

> Hi
>
> Last issue has been fixed and we started to prepare the release
> Apache Ignite 1.5
>

Great news! Thanks, everyone, for the effort put in. Looking forward to the
final release.


>
>
> On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov 
> wrote:
>
> > Yes, sure.
> >
> > On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> If the examples work well with BinaryMarshaller, I think we can push
> this
> >> ticket to 1.6. Thoughts?
> >>
> >> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov 
> >> wrote:
> >>
> >> > It is the way to test optimized marshaller.
> >> > The binary marshaller is a new feature and not very well tested yet
> thus
> >> > optimized marshalling shouldn't be broken for any cases
> >> >
> >> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <
> >> dsetrak...@apache.org>
> >> > wrote:
> >> >
> >> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the
> >> > latest
> >> > > Binary marshaling which should be used by default. Any reason we
> care
> >> > about
> >> > > Optimized marshaller for the examples?
> >> > >
> >> > > D.
> >> > >
> >> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk <
> >> > > alexey.goncha...@gmail.com> wrote:
> >> > >
> >> > > > Igniters,
> >> > > >
> >> > > > Another issue has been reported related to unexpected exception in
> >> > > examples
> >> > > > when optimized marshaller is used:
> >> > > > https://issues.apache.org/jira/browse/IGNITE-2266
> >> > > >
> >> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however
> >> I do
> >> > > not
> >> > > > think it is a blocker for the release.
> >> > > >
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Sergey Kozlov
> >>
> >> >
> >>
> >
> >
> >
> > --
> > Sergey Kozlov
> >
> >
>
>
> --
> Sergey Kozlov
>

Re: 1.5.final

[Sergey Kozlov]

Hi

Last issue has been fixed and we started to prepare the release Apache
Ignite 1.5


On Thu, Dec 24, 2015 at 8:12 PM, Sergey Kozlov  wrote:

> Yes, sure.
>
> On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan 
> wrote:
>
>> If the examples work well with BinaryMarshaller, I think we can push this
>> ticket to 1.6. Thoughts?
>>
>> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov 
>> wrote:
>>
>> > It is the way to test optimized marshaller.
>> > The binary marshaller is a new feature and not very well tested yet thus
>> > optimized marshalling shouldn't be broken for any cases
>> >
>> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <
>> dsetrak...@apache.org>
>> > wrote:
>> >
>> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the
>> > latest
>> > > Binary marshaling which should be used by default. Any reason we care
>> > about
>> > > Optimized marshaller for the examples?
>> > >
>> > > D.
>> > >
>> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk <
>> > > alexey.goncha...@gmail.com> wrote:
>> > >
>> > > > Igniters,
>> > > >
>> > > > Another issue has been reported related to unexpected exception in
>> > > examples
>> > > > when optimized marshaller is used:
>> > > > https://issues.apache.org/jira/browse/IGNITE-2266
>> > > >
>> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however
>> I do
>> > > not
>> > > > think it is a blocker for the release.
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Sergey Kozlov
>>
>> >
>>
>
>
>
> --
> Sergey Kozlov
>
>


-- 
Sergey Kozlov

Re: 1.5.final

[Sergey Kozlov]

Yes, sure.

On Thu, Dec 24, 2015 at 8:09 PM, Dmitriy Setrakyan 
wrote:

> If the examples work well with BinaryMarshaller, I think we can push this
> ticket to 1.6. Thoughts?
>
> On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov 
> wrote:
>
> > It is the way to test optimized marshaller.
> > The binary marshaller is a new feature and not very well tested yet thus
> > optimized marshalling shouldn't be broken for any cases
> >
> > On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> > > I am seeing that IGNITE-2266 is about Optimized marshaller, not the
> > latest
> > > Binary marshaling which should be used by default. Any reason we care
> > about
> > > Optimized marshaller for the examples?
> > >
> > > D.
> > >
> > > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com> wrote:
> > >
> > > > Igniters,
> > > >
> > > > Another issue has been reported related to unexpected exception in
> > > examples
> > > > when optimized marshaller is used:
> > > > https://issues.apache.org/jira/browse/IGNITE-2266
> > > >
> > > > I will try to fix this before 2257 is fixed to fit in 1.5, however I
> do
> > > not
> > > > think it is a blocker for the release.
> > > >
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> > GridGain Systems
> > www.gridgain.com
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

Re: 1.5.final

[Dmitriy Setrakyan]

If the examples work well with BinaryMarshaller, I think we can push this
ticket to 1.6. Thoughts?

On Thu, Dec 24, 2015 at 9:07 AM, Sergey Kozlov  wrote:

> It is the way to test optimized marshaller.
> The binary marshaller is a new feature and not very well tested yet thus
> optimized marshalling shouldn't be broken for any cases
>
> On Thu, Dec 24, 2015 at 8:00 PM, Dmitriy Setrakyan 
> wrote:
>
> > I am seeing that IGNITE-2266 is about Optimized marshaller, not the
> latest
> > Binary marshaling which should be used by default. Any reason we care
> about
> > Optimized marshaller for the examples?
> >
> > D.
> >
> > On Thu, Dec 24, 2015 at 7:29 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > Igniters,
> > >
> > > Another issue has been reported related to unexpected exception in
> > examples
> > > when optimized marshaller is used:
> > > https://issues.apache.org/jira/browse/IGNITE-2266
> > >
> > > I will try to fix this before 2257 is fixed to fit in 1.5, however I do
> > not
> > > think it is a blocker for the release.
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Re: 1.5.final

[Alexey Kuznetsov]

IGNITE-2252 Add support for cache sql schema in REST topology command

Fixed, tested, docs updated and merged into release branch.

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: 1.5.final

[Sergey Kozlov]

Hi

It's the last ticket from the list provided yesterday. But today we found
yet another blocker issue and now we're working on it:

IGNITE-2257 Incorrect deserialization of BinaryContext.


On Thu, Dec 24, 2015 at 2:24 PM, Alexey Kuznetsov 
wrote:

> IGNITE-2252 Add support for cache sql schema in REST topology command
>
> Fixed, tested, docs updated and merged into release branch.
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>



-- 
Sergey Kozlov

Re: 1.5.final

[Alexey Goncharuk]

Igniters,

Another issue has been reported related to unexpected exception in examples
when optimized marshaller is used:
https://issues.apache.org/jira/browse/IGNITE-2266

I will try to fix this before 2257 is fixed to fit in 1.5, however I do not
think it is a blocker for the release.

Re: 1.5.final

[Alexey Goncharuk]

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

Re: 1.5.final

[Sergey Kozlov]

Hi Igniters
We've great progress and only two outstanding issues prevents to release:
IGNITE-2252 Add support for cache sql schema in REST topology command

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 3:10 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

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



-- 
Sergey Kozlov

Re: 1.5.final

[Dmitriy Setrakyan]

Got it. Looks like this is the only remaining issue. Please let us know
here once you fix it, so we could start voting on the final release.

On Wed, Dec 23, 2015 at 9:22 AM, Alexey Kuznetsov 
wrote:

> No, this is not old issue, new cache configuration property "SQL schema"
> was merged into ignite-1.5  two days ago.
>
> I would like to fix in ignite-1.5 in order to be able to execute SQL
> queries from Ignite console against ignite-1.5 cluster.
>
> New "SQL schema" cache configuration property implemented in such a way
> that if user specify it
>  then cache name can not be used as "schema name" any more only specified
> schema name.
>
> So, we need to show sql schema on web console UI and use it for building
> SQL queries.
>
> Please, take a look at this thread
>
> http://apache-ignite-developers.2346864.n4.nabble.com/sqlSchema-usability-question-td6133.html
> Where sql schema usability was discussed.
>
> On Thu, Dec 24, 2015 at 12:14 AM, Dmitriy Setrakyan  >
> wrote:
>
> > On Wed, Dec 23, 2015 at 5:30 AM, Alexey Kuznetsov <
> akuznet...@gridgain.com
> > >
> > wrote:
> >
> > > I think "IGNITE-2252 Add support for cache sql schema in REST topology
> > > command" will be fixed tomorrow in first half of a day.
> > >
> >
> > This looks like an old issue. Is there a reason why this ticket is so
> > critical for 1.5 release?
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: 1.5.final

[Anton Vinogradov]

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

On Wed, Dec 23, 2015 at 4:30 PM, Alexey Kuznetsov 
wrote:

> I think "IGNITE-2252 Add support for cache sql schema in REST topology
> command" will be fixed tomorrow in first half of a day.
>
> On Wed, Dec 23, 2015 at 7:14 PM, Sergey Kozlov 
> wrote:
>
> > Hi Igniters
> > We've great progress and only two outstanding issues prevents to release:
> > IGNITE-2252 Add support for cache sql schema in REST topology command
> > 
> > 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 3:10 PM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> > > The fix for https://issues.apache.org/jira/browse/IGNITE-2200 has been
> > > merged to ignite-1.5​
> > >
> >
> >
> >
> > --
> > Sergey Kozlov
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

Re: 1.5.final

[Alexey Kuznetsov]

No, this is not old issue, new cache configuration property "SQL schema"
was merged into ignite-1.5  two days ago.

I would like to fix in ignite-1.5 in order to be able to execute SQL
queries from Ignite console against ignite-1.5 cluster.

New "SQL schema" cache configuration property implemented in such a way
that if user specify it
 then cache name can not be used as "schema name" any more only specified
schema name.

So, we need to show sql schema on web console UI and use it for building
SQL queries.

Please, take a look at this thread
http://apache-ignite-developers.2346864.n4.nabble.com/sqlSchema-usability-question-td6133.html
Where sql schema usability was discussed.

On Thu, Dec 24, 2015 at 12:14 AM, Dmitriy Setrakyan 
wrote:

> On Wed, Dec 23, 2015 at 5:30 AM, Alexey Kuznetsov  >
> wrote:
>
> > I think "IGNITE-2252 Add support for cache sql schema in REST topology
> > command" will be fixed tomorrow in first half of a day.
> >
>
> This looks like an old issue. Is there a reason why this ticket is so
> critical for 1.5 release?
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: 1.5.final

[Dmitriy Setrakyan]

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 <
alexey.goncha...@gmail.com> 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.
>

Re: 1.5.final

[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 
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 <
> alexey.goncha...@gmail.com> 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.
> >
>

Re: 1.5.final

[Dmitriy Setrakyan]

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

Re: 1.5.final

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

Re: 1.5.final

[Alexey Goncharuk]

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

Re: 1.5.final

[Raul Kripalani]

On Tue, Dec 22, 2015 at 9:25 AM, Anton Vinogradov 
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

Re: 1.5.final

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

Re: 1.5.final

[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 
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 
> 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 <
> > alexey.goncha...@gmail.com> 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.
> > >
> >
>

Re: 1.5.final

[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 
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 <
> alexey.goncha...@gmail.com> 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" 
> 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.
> > >
> >
>

Re: 1.5.final

[Dmitriy Setrakyan]

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 <
valentin.kuliche...@gmail.com> 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 
> 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 <
> > alexey.goncha...@gmail.com> 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" 
> > 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.
> > > >
> > >
> >
>

Re: 1.5.final

[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 
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 <
> valentin.kuliche...@gmail.com> 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 <
> dsetrak...@apache.org>
> > 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 <
> > > alexey.goncha...@gmail.com> 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" 
> > > 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.
> > > > >
> > > >
> > >
> >
>

Re: 1.5.final

[Vladimir Ozerov]

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

On Tue, Dec 22, 2015 at 9:00 AM, Vladimir Ozerov 
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 
> 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 <
>> valentin.kuliche...@gmail.com> 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 <
>> dsetrak...@apache.org>
>> > 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 <
>> > > alexey.goncha...@gmail.com> 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" 
>> > > 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.
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Re: 1.5.final

[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 
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 
> 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 <
> > valentin.kuliche...@gmail.com> 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 <
> > dsetrak...@apache.org>
> > > 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 <
> > > > alexey.goncha...@gmail.com> 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" 
> > > > 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.
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: 1.5.final

[Konstantin Boudnik]

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.


signature.asc
Description: Digital signature

Re: 1.5.final

[Dmitriy Setrakyan]

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

Re: 1.5.final

[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"  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.
>

Re: 1.5.final

[Dmitriy Setrakyan]

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 <
alexey.goncha...@gmail.com> 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"  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.
> >
>