Ignite-1.5 Release

classic Classic list List threaded Threaded
108 messages Options
1234 ... 6
Reply | Threaded
Open this post in threaded view
|

Ignite-1.5 Release

yzhdanov
Guys,

I think we can start preparation to Ignite-1.5 release which will include
many interesting features:

1. Portable object API
https://issues.apache.org/jira/browse/IGNITE-1486

2. Ignite.NET and Ignite C++
https://issues.apache.org/jira/browse/IGNITE-1282

3. Optimistic serializable transactions
https://issues.apache.org/jira/browse/IGNITE-1607

4. Distributed SQL joins - we will be able to query non-collocated data as
well
https://issues.apache.org/jira/browse/IGNITE-1232

5. Enhanced Oracle and IBM JDK interoperability
https://issues.apache.org/jira/browse/IGNITE-1526

6. MQTT streamer
https://issues.apache.org/jira/browse/IGNITE-535

7. Continuous query failover
https://issues.apache.org/jira/browse/IGNITE-426

8. Significant transactional cache performance optimizations - I will merge
these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.

9. Many stability and fault-tolerance fixes.

10. I would also like to include distributed Semaphore. Vladislav, any
chance you can finish with it this week?
https://issues.apache.org/jira/browse/IGNITE-
<https://issues.apache.org/jira/browse/IGNITE-426>638

Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
please respond to this email and let us know when can we expect your
changes being merged to master and release branch?

Can someone create ignite-1.5 release branch?

--Yakov
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Anton Vinogradov
I assume that correct link at 10th feature is
https://issues.apache.org/jira/browse/IGNITE-638

On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]> wrote:

> Guys,
>
> I think we can start preparation to Ignite-1.5 release which will include
> many interesting features:
>
> 1. Portable object API
> https://issues.apache.org/jira/browse/IGNITE-1486
>
> 2. Ignite.NET and Ignite C++
> https://issues.apache.org/jira/browse/IGNITE-1282
>
> 3. Optimistic serializable transactions
> https://issues.apache.org/jira/browse/IGNITE-1607
>
> 4. Distributed SQL joins - we will be able to query non-collocated data as
> well
> https://issues.apache.org/jira/browse/IGNITE-1232
>
> 5. Enhanced Oracle and IBM JDK interoperability
> https://issues.apache.org/jira/browse/IGNITE-1526
>
> 6. MQTT streamer
> https://issues.apache.org/jira/browse/IGNITE-535
>
> 7. Continuous query failover
> https://issues.apache.org/jira/browse/IGNITE-426
>
> 8. Significant transactional cache performance optimizations - I will merge
> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>
> 9. Many stability and fault-tolerance fixes.
>
> 10. I would also like to include distributed Semaphore. Vladislav, any
> chance you can finish with it this week?
> https://issues.apache.org/jira/browse/IGNITE-
> <https://issues.apache.org/jira/browse/IGNITE-426>638
>
> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> please respond to this email and let us know when can we expect your
> changes being merged to master and release branch?
>
> Can someone create ignite-1.5 release branch?
>
> --Yakov
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Anton Vinogradov
Branch ignite-1.5 created.

On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <[hidden email]>
wrote:

> I assume that correct link at 10th feature is
> https://issues.apache.org/jira/browse/IGNITE-638
>
> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]> wrote:
>
>> Guys,
>>
>> I think we can start preparation to Ignite-1.5 release which will include
>> many interesting features:
>>
>> 1. Portable object API
>> https://issues.apache.org/jira/browse/IGNITE-1486
>>
>> 2. Ignite.NET and Ignite C++
>> https://issues.apache.org/jira/browse/IGNITE-1282
>>
>> 3. Optimistic serializable transactions
>> https://issues.apache.org/jira/browse/IGNITE-1607
>>
>> 4. Distributed SQL joins - we will be able to query non-collocated data as
>> well
>> https://issues.apache.org/jira/browse/IGNITE-1232
>>
>> 5. Enhanced Oracle and IBM JDK interoperability
>> https://issues.apache.org/jira/browse/IGNITE-1526
>>
>> 6. MQTT streamer
>> https://issues.apache.org/jira/browse/IGNITE-535
>>
>> 7. Continuous query failover
>> https://issues.apache.org/jira/browse/IGNITE-426
>>
>> 8. Significant transactional cache performance optimizations - I will
>> merge
>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>
>> 9. Many stability and fault-tolerance fixes.
>>
>> 10. I would also like to include distributed Semaphore. Vladislav, any
>> chance you can finish with it this week?
>> https://issues.apache.org/jira/browse/IGNITE-
>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>
>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>> please respond to this email and let us know when can we expect your
>> changes being merged to master and release branch?
>>
>> Can someone create ignite-1.5 release branch?
>>
>> --Yakov
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

endianignite
Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?

On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <[hidden email]>
wrote:

> Branch ignite-1.5 created.
>
> On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <[hidden email]
> >
> wrote:
>
> > I assume that correct link at 10th feature is
> > https://issues.apache.org/jira/browse/IGNITE-638
> >
> > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]>
> wrote:
> >
> >> Guys,
> >>
> >> I think we can start preparation to Ignite-1.5 release which will
> include
> >> many interesting features:
> >>
> >> 1. Portable object API
> >> https://issues.apache.org/jira/browse/IGNITE-1486
> >>
> >> 2. Ignite.NET and Ignite C++
> >> https://issues.apache.org/jira/browse/IGNITE-1282
> >>
> >> 3. Optimistic serializable transactions
> >> https://issues.apache.org/jira/browse/IGNITE-1607
> >>
> >> 4. Distributed SQL joins - we will be able to query non-collocated data
> as
> >> well
> >> https://issues.apache.org/jira/browse/IGNITE-1232
> >>
> >> 5. Enhanced Oracle and IBM JDK interoperability
> >> https://issues.apache.org/jira/browse/IGNITE-1526
> >>
> >> 6. MQTT streamer
> >> https://issues.apache.org/jira/browse/IGNITE-535
> >>
> >> 7. Continuous query failover
> >> https://issues.apache.org/jira/browse/IGNITE-426
> >>
> >> 8. Significant transactional cache performance optimizations - I will
> >> merge
> >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> >>
> >> 9. Many stability and fault-tolerance fixes.
> >>
> >> 10. I would also like to include distributed Semaphore. Vladislav, any
> >> chance you can finish with it this week?
> >> https://issues.apache.org/jira/browse/IGNITE-
> >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> >>
> >> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> >> please respond to this email and let us know when can we expect your
> >> changes being merged to master and release branch?
> >>
> >> Can someone create ignite-1.5 release branch?
> >>
> >> --Yakov
> >>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

dsetrakyan
On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:

> Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?
>

I don’t see why not. Would be nice if one of the committers could pick up
the review for this patch.


>
> On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <[hidden email]
> >
> wrote:
>
> > Branch ignite-1.5 created.
> >
> > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> [hidden email]
> > >
> > wrote:
> >
> > > I assume that correct link at 10th feature is
> > > https://issues.apache.org/jira/browse/IGNITE-638
> > >
> > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]>
> > wrote:
> > >
> > >> Guys,
> > >>
> > >> I think we can start preparation to Ignite-1.5 release which will
> > include
> > >> many interesting features:
> > >>
> > >> 1. Portable object API
> > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > >>
> > >> 2. Ignite.NET and Ignite C++
> > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > >>
> > >> 3. Optimistic serializable transactions
> > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > >>
> > >> 4. Distributed SQL joins - we will be able to query non-collocated
> data
> > as
> > >> well
> > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > >>
> > >> 5. Enhanced Oracle and IBM JDK interoperability
> > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > >>
> > >> 6. MQTT streamer
> > >> https://issues.apache.org/jira/browse/IGNITE-535
> > >>
> > >> 7. Continuous query failover
> > >> https://issues.apache.org/jira/browse/IGNITE-426
> > >>
> > >> 8. Significant transactional cache performance optimizations - I will
> > >> merge
> > >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > >>
> > >> 9. Many stability and fault-tolerance fixes.
> > >>
> > >> 10. I would also like to include distributed Semaphore. Vladislav, any
> > >> chance you can finish with it this week?
> > >> https://issues.apache.org/jira/browse/IGNITE-
> > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > >>
> > >> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
> > >> please respond to this email and let us know when can we expect your
> > >> changes being merged to master and release branch?
> > >>
> > >> Can someone create ignite-1.5 release branch?
> > >>
> > >> --Yakov
> > >>
> > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Vladisav Jelisavcic
>10. I would also like to include distributed Semaphore. Vladislav, any
>chance you can finish with it this week?
>https://issues.apache.org/jira/browse/IGNITE-
><https://issues.apache.org/jira/browse/IGNITE-426>638

I will have it done by thursday.

Best regards,
Vladisav

On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
>
> > Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681
> ?
> >
>
> I don’t see why not. Would be nice if one of the committers could pick up
> the review for this patch.
>
>
> >
> > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> [hidden email]
> > >
> > wrote:
> >
> > > Branch ignite-1.5 created.
> > >
> > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > [hidden email]
> > > >
> > > wrote:
> > >
> > > > I assume that correct link at 10th feature is
> > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > >
> > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]>
> > > wrote:
> > > >
> > > >> Guys,
> > > >>
> > > >> I think we can start preparation to Ignite-1.5 release which will
> > > include
> > > >> many interesting features:
> > > >>
> > > >> 1. Portable object API
> > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > >>
> > > >> 2. Ignite.NET and Ignite C++
> > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > >>
> > > >> 3. Optimistic serializable transactions
> > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > >>
> > > >> 4. Distributed SQL joins - we will be able to query non-collocated
> > data
> > > as
> > > >> well
> > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > >>
> > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > >>
> > > >> 6. MQTT streamer
> > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > >>
> > > >> 7. Continuous query failover
> > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > >>
> > > >> 8. Significant transactional cache performance optimizations - I
> will
> > > >> merge
> > > >> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
> > > >>
> > > >> 9. Many stability and fault-tolerance fixes.
> > > >>
> > > >> 10. I would also like to include distributed Semaphore. Vladislav,
> any
> > > >> chance you can finish with it this week?
> > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >>
> > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> issues,
> > > >> please respond to this email and let us know when can we expect your
> > > >> changes being merged to master and release branch?
> > > >>
> > > >> Can someone create ignite-1.5 release branch?
> > > >>
> > > >> --Yakov
> > > >>
> > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

dsetrakyan
Thanks Vladislav!

Would also be nice to get an update from other committers involved in the
outlined tickets. Specifically whether the ticket has been merged to master
or not, and if not, what should be the expectation.

Thanks,
D.

On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <[hidden email]>
wrote:

> >10. I would also like to include distributed Semaphore. Vladislav, any
> >chance you can finish with it this week?
> >https://issues.apache.org/jira/browse/IGNITE-
> ><https://issues.apache.org/jira/browse/IGNITE-426>638
>
> I will have it done by thursday.
>
> Best regards,
> Vladisav
>
> On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
> >
> > > Can/will this include
> https://issues.apache.org/jira/browse/IGNITE-1681
> > ?
> > >
> >
> > I don’t see why not. Would be nice if one of the committers could pick up
> > the review for this patch.
> >
> >
> > >
> > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > [hidden email]
> > > >
> > > wrote:
> > >
> > > > Branch ignite-1.5 created.
> > > >
> > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > [hidden email]
> > > > >
> > > > wrote:
> > > >
> > > > > I assume that correct link at 10th feature is
> > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]
> >
> > > > wrote:
> > > > >
> > > > >> Guys,
> > > > >>
> > > > >> I think we can start preparation to Ignite-1.5 release which will
> > > > include
> > > > >> many interesting features:
> > > > >>
> > > > >> 1. Portable object API
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > >>
> > > > >> 2. Ignite.NET and Ignite C++
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > >>
> > > > >> 3. Optimistic serializable transactions
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > >>
> > > > >> 4. Distributed SQL joins - we will be able to query non-collocated
> > > data
> > > > as
> > > > >> well
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > >>
> > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > >>
> > > > >> 6. MQTT streamer
> > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > >>
> > > > >> 7. Continuous query failover
> > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > >>
> > > > >> 8. Significant transactional cache performance optimizations - I
> > will
> > > > >> merge
> > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> tomorrow.
> > > > >>
> > > > >> 9. Many stability and fault-tolerance fixes.
> > > > >>
> > > > >> 10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > > >> chance you can finish with it this week?
> > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >>
> > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > issues,
> > > > >> please respond to this email and let us know when can we expect
> your
> > > > >> changes being merged to master and release branch?
> > > > >>
> > > > >> Can someone create ignite-1.5 release branch?
> > > > >>
> > > > >> --Yakov
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Goncharuk
I am finalizing changes related to IGNITE-1486 branch. Currently the API
changes are finished and now I am mostly fixing the CI tests. In fact, I
just submitted the latest fix related to the new .NET platform
functionality and hope CI tests will pass, in this case it will be ready to
be merged tomorrow morning.
It would be nice if other community members reviewed my changes in
ignite-950-new branch before it gets to master.

2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:

> Thanks Vladislav!
>
> Would also be nice to get an update from other committers involved in the
> outlined tickets. Specifically whether the ticket has been merged to master
> or not, and if not, what should be the expectation.
>
> Thanks,
> D.
>
> On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <[hidden email]>
> wrote:
>
> > >10. I would also like to include distributed Semaphore. Vladislav, any
> > >chance you can finish with it this week?
> > >https://issues.apache.org/jira/browse/IGNITE-
> > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> >
> > I will have it done by thursday.
> >
> > Best regards,
> > Vladisav
> >
> > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <[hidden email]
> >
> > wrote:
> >
> > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
> > >
> > > > Can/will this include
> > https://issues.apache.org/jira/browse/IGNITE-1681
> > > ?
> > > >
> > >
> > > I don’t see why not. Would be nice if one of the committers could pick
> up
> > > the review for this patch.
> > >
> > >
> > > >
> > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > [hidden email]
> > > > >
> > > > wrote:
> > > >
> > > > > Branch ignite-1.5 created.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > [hidden email]
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > I assume that correct link at 10th feature is
> > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> [hidden email]
> > >
> > > > > wrote:
> > > > > >
> > > > > >> Guys,
> > > > > >>
> > > > > >> I think we can start preparation to Ignite-1.5 release which
> will
> > > > > include
> > > > > >> many interesting features:
> > > > > >>
> > > > > >> 1. Portable object API
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > >>
> > > > > >> 2. Ignite.NET and Ignite C++
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > >>
> > > > > >> 3. Optimistic serializable transactions
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > >>
> > > > > >> 4. Distributed SQL joins - we will be able to query
> non-collocated
> > > > data
> > > > > as
> > > > > >> well
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > >>
> > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > >>
> > > > > >> 6. MQTT streamer
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > >>
> > > > > >> 7. Continuous query failover
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > >>
> > > > > >> 8. Significant transactional cache performance optimizations - I
> > > will
> > > > > >> merge
> > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > tomorrow.
> > > > > >>
> > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > >>
> > > > > >> 10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > > >> chance you can finish with it this week?
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >>
> > > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > issues,
> > > > > >> please respond to this email and let us know when can we expect
> > your
> > > > > >> changes being merged to master and release branch?
> > > > > >>
> > > > > >> Can someone create ignite-1.5 release branch?
> > > > > >>
> > > > > >> --Yakov
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

dsetrakyan
Alexey,

I am confused. Why do you have 2 branches?

D.

On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <[hidden email]
> wrote:

> I am finalizing changes related to IGNITE-1486 branch. Currently the API
> changes are finished and now I am mostly fixing the CI tests. In fact, I
> just submitted the latest fix related to the new .NET platform
> functionality and hope CI tests will pass, in this case it will be ready to
> be merged tomorrow morning.
> It would be nice if other community members reviewed my changes in
> ignite-950-new branch before it gets to master.
>
> 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
>
> > Thanks Vladislav!
> >
> > Would also be nice to get an update from other committers involved in the
> > outlined tickets. Specifically whether the ticket has been merged to
> master
> > or not, and if not, what should be the expectation.
> >
> > Thanks,
> > D.
> >
> > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> [hidden email]>
> > wrote:
> >
> > > >10. I would also like to include distributed Semaphore. Vladislav, any
> > > >chance you can finish with it this week?
> > > >https://issues.apache.org/jira/browse/IGNITE-
> > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > >
> > > I will have it done by thursday.
> > >
> > > Best regards,
> > > Vladisav
> > >
> > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> [hidden email]
> > >
> > > wrote:
> > >
> > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
> > > >
> > > > > Can/will this include
> > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > ?
> > > > >
> > > >
> > > > I don’t see why not. Would be nice if one of the committers could
> pick
> > up
> > > > the review for this patch.
> > > >
> > > >
> > > > >
> > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > [hidden email]
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > Branch ignite-1.5 created.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > [hidden email]
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > I assume that correct link at 10th feature is
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > [hidden email]
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > >> Guys,
> > > > > > >>
> > > > > > >> I think we can start preparation to Ignite-1.5 release which
> > will
> > > > > > include
> > > > > > >> many interesting features:
> > > > > > >>
> > > > > > >> 1. Portable object API
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > >>
> > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > >>
> > > > > > >> 3. Optimistic serializable transactions
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > >>
> > > > > > >> 4. Distributed SQL joins - we will be able to query
> > non-collocated
> > > > > data
> > > > > > as
> > > > > > >> well
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > >>
> > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > >>
> > > > > > >> 6. MQTT streamer
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > >>
> > > > > > >> 7. Continuous query failover
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > >>
> > > > > > >> 8. Significant transactional cache performance optimizations
> - I
> > > > will
> > > > > > >> merge
> > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > tomorrow.
> > > > > > >>
> > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > >>
> > > > > > >> 10. I would also like to include distributed Semaphore.
> > Vladislav,
> > > > any
> > > > > > >> chance you can finish with it this week?
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > >>
> > > > > > >> Thanks to everyone involved! Guys, esp. assignees of mentioned
> > > > issues,
> > > > > > >> please respond to this email and let us know when can we
> expect
> > > your
> > > > > > >> changes being merged to master and release branch?
> > > > > > >>
> > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > >>
> > > > > > >> --Yakov
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Goncharuk
I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*". The
changes are in ignite-950-new branch because it is a result of work on
multiple sub-tickets and it is currently used as an integration branch.

2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:

> Alexey,
>
> I am confused. Why do you have 2 branches?
>
> D.
>
> On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > I am finalizing changes related to IGNITE-1486 branch. Currently the API
> > changes are finished and now I am mostly fixing the CI tests. In fact, I
> > just submitted the latest fix related to the new .NET platform
> > functionality and hope CI tests will pass, in this case it will be ready
> to
> > be merged tomorrow morning.
> > It would be nice if other community members reviewed my changes in
> > ignite-950-new branch before it gets to master.
> >
> > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> >
> > > Thanks Vladislav!
> > >
> > > Would also be nice to get an update from other committers involved in
> the
> > > outlined tickets. Specifically whether the ticket has been merged to
> > master
> > > or not, and if not, what should be the expectation.
> > >
> > > Thanks,
> > > D.
> > >
> > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > [hidden email]>
> > > wrote:
> > >
> > > > >10. I would also like to include distributed Semaphore. Vladislav,
> any
> > > > >chance you can finish with it this week?
> > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > >
> > > > I will have it done by thursday.
> > > >
> > > > Best regards,
> > > > Vladisav
> > > >
> > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > [hidden email]
> > > >
> > > > wrote:
> > > >
> > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
> > > > >
> > > > > > Can/will this include
> > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > ?
> > > > > >
> > > > >
> > > > > I don’t see why not. Would be nice if one of the committers could
> > pick
> > > up
> > > > > the review for this patch.
> > > > >
> > > > >
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > [hidden email]
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Branch ignite-1.5 created.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > [hidden email]
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Guys,
> > > > > > > >>
> > > > > > > >> I think we can start preparation to Ignite-1.5 release which
> > > will
> > > > > > > include
> > > > > > > >> many interesting features:
> > > > > > > >>
> > > > > > > >> 1. Portable object API
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > >>
> > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > >>
> > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > >>
> > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > non-collocated
> > > > > > data
> > > > > > > as
> > > > > > > >> well
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > >>
> > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > >>
> > > > > > > >> 6. MQTT streamer
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > >>
> > > > > > > >> 7. Continuous query failover
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > >>
> > > > > > > >> 8. Significant transactional cache performance optimizations
> > - I
> > > > > will
> > > > > > > >> merge
> > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > > tomorrow.
> > > > > > > >>
> > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > >>
> > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > >> chance you can finish with it this week?
> > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >>
> > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> mentioned
> > > > > issues,
> > > > > > > >> please respond to this email and let us know when can we
> > expect
> > > > your
> > > > > > > >> changes being merged to master and release branch?
> > > > > > > >>
> > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > >>
> > > > > > > >> --Yakov
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Denis Magda
In reply to this post by dsetrakyan


On 11/2/2015 8:40 PM, Dmitriy Setrakyan wrote:
> On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
>
>> Can/will this include https://issues.apache.org/jira/browse/IGNITE-1681 ?
>>
> I don’t see why not. Would be nice if one of the committers could pick up
> the review for this patch.
>
Dmitriy and other committers, who keep an eye on public API changes, are
you OK with the changes in CacheConfiguration API done in IGNITE-1681?

--
Denis

>> On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <[hidden email]
>> wrote:
>>
>>> Branch ignite-1.5 created.
>>>
>>> On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
>> [hidden email]
>>> wrote:
>>>
>>>> I assume that correct link at 10th feature is
>>>> https://issues.apache.org/jira/browse/IGNITE-638
>>>>
>>>> On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <[hidden email]>
>>> wrote:
>>>>> Guys,
>>>>>
>>>>> I think we can start preparation to Ignite-1.5 release which will
>>> include
>>>>> many interesting features:
>>>>>
>>>>> 1. Portable object API
>>>>> https://issues.apache.org/jira/browse/IGNITE-1486
>>>>>
>>>>> 2. Ignite.NET and Ignite C++
>>>>> https://issues.apache.org/jira/browse/IGNITE-1282
>>>>>
>>>>> 3. Optimistic serializable transactions
>>>>> https://issues.apache.org/jira/browse/IGNITE-1607
>>>>>
>>>>> 4. Distributed SQL joins - we will be able to query non-collocated
>> data
>>> as
>>>>> well
>>>>> https://issues.apache.org/jira/browse/IGNITE-1232
>>>>>
>>>>> 5. Enhanced Oracle and IBM JDK interoperability
>>>>> https://issues.apache.org/jira/browse/IGNITE-1526
>>>>>
>>>>> 6. MQTT streamer
>>>>> https://issues.apache.org/jira/browse/IGNITE-535
>>>>>
>>>>> 7. Continuous query failover
>>>>> https://issues.apache.org/jira/browse/IGNITE-426
>>>>>
>>>>> 8. Significant transactional cache performance optimizations - I will
>>>>> merge
>>>>> these changes from 'ignite-1.4-slow-server-debug' today or tomorrow.
>>>>>
>>>>> 9. Many stability and fault-tolerance fixes.
>>>>>
>>>>> 10. I would also like to include distributed Semaphore. Vladislav, any
>>>>> chance you can finish with it this week?
>>>>> https://issues.apache.org/jira/browse/IGNITE-
>>>>> <https://issues.apache.org/jira/browse/IGNITE-426>638
>>>>>
>>>>> Thanks to everyone involved! Guys, esp. assignees of mentioned issues,
>>>>> please respond to this email and let us know when can we expect your
>>>>> changes being merged to master and release branch?
>>>>>
>>>>> Can someone create ignite-1.5 release branch?
>>>>>
>>>>> --Yakov
>>>>>
>>>>

Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Vladimir Ozerov
In reply to this post by Alexey Goncharuk
Here are my current status for all interop-related stuff (you can view
these tickets using query "project = IGNITE AND status in (Open, "In
Progress", Reopened, Resolved, "Patch Available") AND component = interop
AND fixVersion = 1.5"):

*IGNITE-1819 - Remove metadataEnabled flag in Java*
Trivial. Waiting for IGNITE-950 merge.

*IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
Trivial. Waiting for IGNITE-950 merge.

*IGNITE-1803 - Optimized field lookup for queries*
Ready. Waiting for IGNITE-950 to merge.

*IGNITE-1847 - Add "field" method to portable metadata.*
Not started yet. Waiting for IGNITE-950 to merge.

*IGNITE-1816 - Optionally do not write field IDs to portable object footer.*
Not started yet.

+ Several minor tickets.

All in all, I expect all these tickets to be ready in 2 days.



On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <[hidden email]
> wrote:

> I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*". The
> changes are in ignite-950-new branch because it is a result of work on
> multiple sub-tickets and it is currently used as an integration branch.
>
> 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
>
> > Alexey,
> >
> > I am confused. Why do you have 2 branches?
> >
> > D.
> >
> > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > [hidden email]
> > > wrote:
> >
> > > I am finalizing changes related to IGNITE-1486 branch. Currently the
> API
> > > changes are finished and now I am mostly fixing the CI tests. In fact,
> I
> > > just submitted the latest fix related to the new .NET platform
> > > functionality and hope CI tests will pass, in this case it will be
> ready
> > to
> > > be merged tomorrow morning.
> > > It would be nice if other community members reviewed my changes in
> > > ignite-950-new branch before it gets to master.
> > >
> > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > >
> > > > Thanks Vladislav!
> > > >
> > > > Would also be nice to get an update from other committers involved in
> > the
> > > > outlined tickets. Specifically whether the ticket has been merged to
> > > master
> > > > or not, and if not, what should be the expectation.
> > > >
> > > > Thanks,
> > > > D.
> > > >
> > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > [hidden email]>
> > > > wrote:
> > > >
> > > > > >10. I would also like to include distributed Semaphore. Vladislav,
> > any
> > > > > >chance you can finish with it this week?
> > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > >
> > > > > I will have it done by thursday.
> > > > >
> > > > > Best regards,
> > > > > Vladisav
> > > > >
> > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > [hidden email]
> > > > >
> > > > > wrote:
> > > > >
> > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]> wrote:
> > > > > >
> > > > > > > Can/will this include
> > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > ?
> > > > > > >
> > > > > >
> > > > > > I don’t see why not. Would be nice if one of the committers could
> > > pick
> > > > up
> > > > > > the review for this patch.
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Branch ignite-1.5 created.
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > [hidden email]
> > > > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> Guys,
> > > > > > > > >>
> > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> which
> > > > will
> > > > > > > > include
> > > > > > > > >> many interesting features:
> > > > > > > > >>
> > > > > > > > >> 1. Portable object API
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > >>
> > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > >>
> > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > >>
> > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > non-collocated
> > > > > > > data
> > > > > > > > as
> > > > > > > > >> well
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > >>
> > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > >>
> > > > > > > > >> 6. MQTT streamer
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > >>
> > > > > > > > >> 7. Continuous query failover
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > >>
> > > > > > > > >> 8. Significant transactional cache performance
> optimizations
> > > - I
> > > > > > will
> > > > > > > > >> merge
> > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today or
> > > > > tomorrow.
> > > > > > > > >>
> > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > >>
> > > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > > Vladislav,
> > > > > > any
> > > > > > > > >> chance you can finish with it this week?
> > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > >>
> > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > mentioned
> > > > > > issues,
> > > > > > > > >> please respond to this email and let us know when can we
> > > expect
> > > > > your
> > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > >>
> > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > >>
> > > > > > > > >> --Yakov
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Goncharuk
IGNITE-950 is taking more time to be merged than I originally estimated. We
had a couple of silly bugs, such as loosing cache operation context on
async cache operations, which led to hard-to debug failures in the platform
integration code.
I also added some sanity checks to indexing and found that I ran benchmarks
for new binary format on a model with externalizable classes, so the result
I've got were invalid, need more time to fix the model and re-run
benchmarks.

I am currently waiting for another CI run, will give an update in several
hours.

2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> Here are my current status for all interop-related stuff (you can view
> these tickets using query "project = IGNITE AND status in (Open, "In
> Progress", Reopened, Resolved, "Patch Available") AND component = interop
> AND fixVersion = 1.5"):
>
> *IGNITE-1819 - Remove metadataEnabled flag in Java*
> Trivial. Waiting for IGNITE-950 merge.
>
> *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> Trivial. Waiting for IGNITE-950 merge.
>
> *IGNITE-1803 - Optimized field lookup for queries*
> Ready. Waiting for IGNITE-950 to merge.
>
> *IGNITE-1847 - Add "field" method to portable metadata.*
> Not started yet. Waiting for IGNITE-950 to merge.
>
> *IGNITE-1816 - Optionally do not write field IDs to portable object
> footer.*
> Not started yet.
>
> + Several minor tickets.
>
> All in all, I expect all these tickets to be ready in 2 days.
>
>
>
> On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*".
> The
> > changes are in ignite-950-new branch because it is a result of work on
> > multiple sub-tickets and it is currently used as an integration branch.
> >
> > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> >
> > > Alexey,
> > >
> > > I am confused. Why do you have 2 branches?
> > >
> > > D.
> > >
> > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > [hidden email]
> > > > wrote:
> > >
> > > > I am finalizing changes related to IGNITE-1486 branch. Currently the
> > API
> > > > changes are finished and now I am mostly fixing the CI tests. In
> fact,
> > I
> > > > just submitted the latest fix related to the new .NET platform
> > > > functionality and hope CI tests will pass, in this case it will be
> > ready
> > > to
> > > > be merged tomorrow morning.
> > > > It would be nice if other community members reviewed my changes in
> > > > ignite-950-new branch before it gets to master.
> > > >
> > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <[hidden email]
> >:
> > > >
> > > > > Thanks Vladislav!
> > > > >
> > > > > Would also be nice to get an update from other committers involved
> in
> > > the
> > > > > outlined tickets. Specifically whether the ticket has been merged
> to
> > > > master
> > > > > or not, and if not, what should be the expectation.
> > > > >
> > > > > Thanks,
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > > > >10. I would also like to include distributed Semaphore.
> Vladislav,
> > > any
> > > > > > >chance you can finish with it this week?
> > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > >
> > > > > > I will have it done by thursday.
> > > > > >
> > > > > > Best regards,
> > > > > > Vladisav
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > [hidden email]
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]>
> wrote:
> > > > > > >
> > > > > > > > Can/will this include
> > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > ?
> > > > > > > >
> > > > > > >
> > > > > > > I don’t see why not. Would be nice if one of the committers
> could
> > > > pick
> > > > > up
> > > > > > > the review for this patch.
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > [hidden email]
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> Guys,
> > > > > > > > > >>
> > > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> > which
> > > > > will
> > > > > > > > > include
> > > > > > > > > >> many interesting features:
> > > > > > > > > >>
> > > > > > > > > >> 1. Portable object API
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > >>
> > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > >>
> > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > >>
> > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > non-collocated
> > > > > > > > data
> > > > > > > > > as
> > > > > > > > > >> well
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > >>
> > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > >>
> > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > >>
> > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > >>
> > > > > > > > > >> 8. Significant transactional cache performance
> > optimizations
> > > > - I
> > > > > > > will
> > > > > > > > > >> merge
> > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug' today
> or
> > > > > > tomorrow.
> > > > > > > > > >>
> > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > >>
> > > > > > > > > >> 10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >>
> > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > mentioned
> > > > > > > issues,
> > > > > > > > > >> please respond to this email and let us know when can we
> > > > expect
> > > > > > your
> > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > >>
> > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > >>
> > > > > > > > > >> --Yakov
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Nikolay Tikhonov
I implemented changes related to IGNITE-426 task. Currently investigating
performance degradation for atomic caches. I expect the ticket to be merged
in 2 days.

On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <[hidden email]
> wrote:

> IGNITE-950 is taking more time to be merged than I originally estimated. We
> had a couple of silly bugs, such as loosing cache operation context on
> async cache operations, which led to hard-to debug failures in the platform
> integration code.
> I also added some sanity checks to indexing and found that I ran benchmarks
> for new binary format on a model with externalizable classes, so the result
> I've got were invalid, need more time to fix the model and re-run
> benchmarks.
>
> I am currently waiting for another CI run, will give an update in several
> hours.
>
> 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > Here are my current status for all interop-related stuff (you can view
> > these tickets using query "project = IGNITE AND status in (Open, "In
> > Progress", Reopened, Resolved, "Patch Available") AND component = interop
> > AND fixVersion = 1.5"):
> >
> > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > Trivial. Waiting for IGNITE-950 merge.
> >
> > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > Trivial. Waiting for IGNITE-950 merge.
> >
> > *IGNITE-1803 - Optimized field lookup for queries*
> > Ready. Waiting for IGNITE-950 to merge.
> >
> > *IGNITE-1847 - Add "field" method to portable metadata.*
> > Not started yet. Waiting for IGNITE-950 to merge.
> >
> > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > footer.*
> > Not started yet.
> >
> > + Several minor tickets.
> >
> > All in all, I expect all these tickets to be ready in 2 days.
> >
> >
> >
> > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > [hidden email]
> > > wrote:
> >
> > > I'm sorry, I meant to write "changes related to IGNITE-1486 *ticket*".
> > The
> > > changes are in ignite-950-new branch because it is a result of work on
> > > multiple sub-tickets and it is currently used as an integration branch.
> > >
> > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > >
> > > > Alexey,
> > > >
> > > > I am confused. Why do you have 2 branches?
> > > >
> > > > D.
> > > >
> > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > [hidden email]
> > > > > wrote:
> > > >
> > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> the
> > > API
> > > > > changes are finished and now I am mostly fixing the CI tests. In
> > fact,
> > > I
> > > > > just submitted the latest fix related to the new .NET platform
> > > > > functionality and hope CI tests will pass, in this case it will be
> > > ready
> > > > to
> > > > > be merged tomorrow morning.
> > > > > It would be nice if other community members reviewed my changes in
> > > > > ignite-950-new branch before it gets to master.
> > > > >
> > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> [hidden email]
> > >:
> > > > >
> > > > > > Thanks Vladislav!
> > > > > >
> > > > > > Would also be nice to get an update from other committers
> involved
> > in
> > > > the
> > > > > > outlined tickets. Specifically whether the ticket has been merged
> > to
> > > > > master
> > > > > > or not, and if not, what should be the expectation.
> > > > > >
> > > > > > Thanks,
> > > > > > D.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > > > >10. I would also like to include distributed Semaphore.
> > Vladislav,
> > > > any
> > > > > > > >chance you can finish with it this week?
> > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > >
> > > > > > > I will have it done by thursday.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Vladisav
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > [hidden email]
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]>
> > wrote:
> > > > > > > >
> > > > > > > > > Can/will this include
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > ?
> > > > > > > > >
> > > > > > > >
> > > > > > > > I don’t see why not. Would be nice if one of the committers
> > could
> > > > > pick
> > > > > > up
> > > > > > > > the review for this patch.
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > [hidden email]
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >> Guys,
> > > > > > > > > > >>
> > > > > > > > > > >> I think we can start preparation to Ignite-1.5 release
> > > which
> > > > > > will
> > > > > > > > > > include
> > > > > > > > > > >> many interesting features:
> > > > > > > > > > >>
> > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > >>
> > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > >>
> > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > >>
> > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > non-collocated
> > > > > > > > > data
> > > > > > > > > > as
> > > > > > > > > > >> well
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > >>
> > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > >>
> > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > >>
> > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > >>
> > > > > > > > > > >> 8. Significant transactional cache performance
> > > optimizations
> > > > > - I
> > > > > > > > will
> > > > > > > > > > >> merge
> > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> today
> > or
> > > > > > > tomorrow.
> > > > > > > > > > >>
> > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > >>
> > > > > > > > > > >> 10. I would also like to include distributed
> Semaphore.
> > > > > > Vladislav,
> > > > > > > > any
> > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > mentioned
> > > > > > > > issues,
> > > > > > > > > > >> please respond to this email and let us know when can
> we
> > > > > expect
> > > > > > > your
> > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > >>
> > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > >>
> > > > > > > > > > >> --Yakov
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Sergi
Guys,

I'm currently struggling with distributed SQL join feature. The main
problem comes from the query optimization side because
when we assume to have everything collocated it is a problem of user to
achieve that, but now we have to:
1. Get to optimal plan which will not use distributed joins if it is
possible to achieve correct result using some collocated plan.
2. Correctly execute that plan because now it not only a question of
performance but also a question of getting correct results.
This all gets quite tricky when we are handling subqueries. Hope to finish
this in a day or two.

Sergi



2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <[hidden email]>:

> I implemented changes related to IGNITE-426 task. Currently investigating
> performance degradation for atomic caches. I expect the ticket to be merged
> in 2 days.
>
> On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > IGNITE-950 is taking more time to be merged than I originally estimated.
> We
> > had a couple of silly bugs, such as loosing cache operation context on
> > async cache operations, which led to hard-to debug failures in the
> platform
> > integration code.
> > I also added some sanity checks to indexing and found that I ran
> benchmarks
> > for new binary format on a model with externalizable classes, so the
> result
> > I've got were invalid, need more time to fix the model and re-run
> > benchmarks.
> >
> > I am currently waiting for another CI run, will give an update in several
> > hours.
> >
> > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> >
> > > Here are my current status for all interop-related stuff (you can view
> > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > Progress", Reopened, Resolved, "Patch Available") AND component =
> interop
> > > AND fixVersion = 1.5"):
> > >
> > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1803 - Optimized field lookup for queries*
> > > Ready. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > Not started yet. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > footer.*
> > > Not started yet.
> > >
> > > + Several minor tickets.
> > >
> > > All in all, I expect all these tickets to be ready in 2 days.
> > >
> > >
> > >
> > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > [hidden email]
> > > > wrote:
> > >
> > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> *ticket*".
> > > The
> > > > changes are in ignite-950-new branch because it is a result of work
> on
> > > > multiple sub-tickets and it is currently used as an integration
> branch.
> > > >
> > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > > >
> > > > > Alexey,
> > > > >
> > > > > I am confused. Why do you have 2 branches?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > [hidden email]
> > > > > > wrote:
> > > > >
> > > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> > the
> > > > API
> > > > > > changes are finished and now I am mostly fixing the CI tests. In
> > > fact,
> > > > I
> > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > functionality and hope CI tests will pass, in this case it will
> be
> > > > ready
> > > > > to
> > > > > > be merged tomorrow morning.
> > > > > > It would be nice if other community members reviewed my changes
> in
> > > > > > ignite-950-new branch before it gets to master.
> > > > > >
> > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > [hidden email]
> > > >:
> > > > > >
> > > > > > > Thanks Vladislav!
> > > > > > >
> > > > > > > Would also be nice to get an update from other committers
> > involved
> > > in
> > > > > the
> > > > > > > outlined tickets. Specifically whether the ticket has been
> merged
> > > to
> > > > > > master
> > > > > > > or not, and if not, what should be the expectation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > [hidden email]>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > >10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > > >chance you can finish with it this week?
> > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >
> > > > > > > > I will have it done by thursday.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Vladisav
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Can/will this include
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > ?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > I don’t see why not. Would be nice if one of the committers
> > > could
> > > > > > pick
> > > > > > > up
> > > > > > > > > the review for this patch.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > [hidden email]
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > [hidden email]
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> Guys,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> release
> > > > which
> > > > > > > will
> > > > > > > > > > > include
> > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > >>
> > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > >>
> > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > >>
> > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > >>
> > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > > non-collocated
> > > > > > > > > > data
> > > > > > > > > > > as
> > > > > > > > > > > >> well
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > >>
> > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > >>
> > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > >>
> > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > >>
> > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > optimizations
> > > > > > - I
> > > > > > > > > will
> > > > > > > > > > > >> merge
> > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > today
> > > or
> > > > > > > > tomorrow.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 10. I would also like to include distributed
> > Semaphore.
> > > > > > > Vladislav,
> > > > > > > > > any
> > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> >638
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > > mentioned
> > > > > > > > > issues,
> > > > > > > > > > > >> please respond to this email and let us know when
> can
> > we
> > > > > > expect
> > > > > > > > your
> > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> --Yakov
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Goncharuk
In reply to this post by Nikolay Tikhonov
Good news for the IGNITE-950 ticket - CI looks good, changes will be merged
to ignite-1282 integration branch after benchmarks re-run.

2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <[hidden email]>:

> I implemented changes related to IGNITE-426 task. Currently investigating
> performance degradation for atomic caches. I expect the ticket to be merged
> in 2 days.
>
> On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > IGNITE-950 is taking more time to be merged than I originally estimated.
> We
> > had a couple of silly bugs, such as loosing cache operation context on
> > async cache operations, which led to hard-to debug failures in the
> platform
> > integration code.
> > I also added some sanity checks to indexing and found that I ran
> benchmarks
> > for new binary format on a model with externalizable classes, so the
> result
> > I've got were invalid, need more time to fix the model and re-run
> > benchmarks.
> >
> > I am currently waiting for another CI run, will give an update in several
> > hours.
> >
> > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> >
> > > Here are my current status for all interop-related stuff (you can view
> > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > Progress", Reopened, Resolved, "Patch Available") AND component =
> interop
> > > AND fixVersion = 1.5"):
> > >
> > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > Trivial. Waiting for IGNITE-950 merge.
> > >
> > > *IGNITE-1803 - Optimized field lookup for queries*
> > > Ready. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > Not started yet. Waiting for IGNITE-950 to merge.
> > >
> > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > footer.*
> > > Not started yet.
> > >
> > > + Several minor tickets.
> > >
> > > All in all, I expect all these tickets to be ready in 2 days.
> > >
> > >
> > >
> > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > [hidden email]
> > > > wrote:
> > >
> > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> *ticket*".
> > > The
> > > > changes are in ignite-950-new branch because it is a result of work
> on
> > > > multiple sub-tickets and it is currently used as an integration
> branch.
> > > >
> > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > > >
> > > > > Alexey,
> > > > >
> > > > > I am confused. Why do you have 2 branches?
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > [hidden email]
> > > > > > wrote:
> > > > >
> > > > > > I am finalizing changes related to IGNITE-1486 branch. Currently
> > the
> > > > API
> > > > > > changes are finished and now I am mostly fixing the CI tests. In
> > > fact,
> > > > I
> > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > functionality and hope CI tests will pass, in this case it will
> be
> > > > ready
> > > > > to
> > > > > > be merged tomorrow morning.
> > > > > > It would be nice if other community members reviewed my changes
> in
> > > > > > ignite-950-new branch before it gets to master.
> > > > > >
> > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > [hidden email]
> > > >:
> > > > > >
> > > > > > > Thanks Vladislav!
> > > > > > >
> > > > > > > Would also be nice to get an update from other committers
> > involved
> > > in
> > > > > the
> > > > > > > outlined tickets. Specifically whether the ticket has been
> merged
> > > to
> > > > > > master
> > > > > > > or not, and if not, what should be the expectation.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > [hidden email]>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > >10. I would also like to include distributed Semaphore.
> > > Vladislav,
> > > > > any
> > > > > > > > >chance you can finish with it this week?
> > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > >
> > > > > > > > I will have it done by thursday.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Vladisav
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]>
> > > wrote:
> > > > > > > > >
> > > > > > > > > > Can/will this include
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > ?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > I don’t see why not. Would be nice if one of the committers
> > > could
> > > > > > pick
> > > > > > > up
> > > > > > > > > the review for this patch.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > [hidden email]
> > > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > [hidden email]
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >> Guys,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> release
> > > > which
> > > > > > > will
> > > > > > > > > > > include
> > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > >>
> > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > >>
> > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > >>
> > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > >>
> > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to query
> > > > > > > non-collocated
> > > > > > > > > > data
> > > > > > > > > > > as
> > > > > > > > > > > >> well
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > >>
> > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > >>
> > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > >>
> > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > >>
> > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > optimizations
> > > > > > - I
> > > > > > > > > will
> > > > > > > > > > > >> merge
> > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > today
> > > or
> > > > > > > > tomorrow.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > >>
> > > > > > > > > > > >> 10. I would also like to include distributed
> > Semaphore.
> > > > > > > Vladislav,
> > > > > > > > > any
> > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> >638
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees of
> > > > > mentioned
> > > > > > > > > issues,
> > > > > > > > > > > >> please respond to this email and let us know when
> can
> > we
> > > > > > expect
> > > > > > > > your
> > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > >>
> > > > > > > > > > > >> --Yakov
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Kuznetsov-2
I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
https://issues.apache.org/jira/browse/IGNITE-1753).
Issue is implemented and waiting for  IGNITE-950 to be merged into
ignite-1282.

On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <[hidden email]
> wrote:

> Good news for the IGNITE-950 ticket - CI looks good, changes will be merged
> to ignite-1282 integration branch after benchmarks re-run.
>
> 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <[hidden email]>:
>
> > I implemented changes related to IGNITE-426 task. Currently investigating
> > performance degradation for atomic caches. I expect the ticket to be
> merged
> > in 2 days.
> >
> > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > [hidden email]
> > > wrote:
> >
> > > IGNITE-950 is taking more time to be merged than I originally
> estimated.
> > We
> > > had a couple of silly bugs, such as loosing cache operation context on
> > > async cache operations, which led to hard-to debug failures in the
> > platform
> > > integration code.
> > > I also added some sanity checks to indexing and found that I ran
> > benchmarks
> > > for new binary format on a model with externalizable classes, so the
> > result
> > > I've got were invalid, need more time to fix the model and re-run
> > > benchmarks.
> > >
> > > I am currently waiting for another CI run, will give an update in
> several
> > > hours.
> > >
> > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> > >
> > > > Here are my current status for all interop-related stuff (you can
> view
> > > > these tickets using query "project = IGNITE AND status in (Open, "In
> > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > interop
> > > > AND fixVersion = 1.5"):
> > > >
> > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > Trivial. Waiting for IGNITE-950 merge.
> > > >
> > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > Trivial. Waiting for IGNITE-950 merge.
> > > >
> > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > Ready. Waiting for IGNITE-950 to merge.
> > > >
> > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > >
> > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > footer.*
> > > > Not started yet.
> > > >
> > > > + Several minor tickets.
> > > >
> > > > All in all, I expect all these tickets to be ready in 2 days.
> > > >
> > > >
> > > >
> > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > [hidden email]
> > > > > wrote:
> > > >
> > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > *ticket*".
> > > > The
> > > > > changes are in ignite-950-new branch because it is a result of work
> > on
> > > > > multiple sub-tickets and it is currently used as an integration
> > branch.
> > > > >
> > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <[hidden email]
> >:
> > > > >
> > > > > > Alexey,
> > > > > >
> > > > > > I am confused. Why do you have 2 branches?
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > [hidden email]
> > > > > > > wrote:
> > > > > >
> > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> Currently
> > > the
> > > > > API
> > > > > > > changes are finished and now I am mostly fixing the CI tests.
> In
> > > > fact,
> > > > > I
> > > > > > > just submitted the latest fix related to the new .NET platform
> > > > > > > functionality and hope CI tests will pass, in this case it will
> > be
> > > > > ready
> > > > > > to
> > > > > > > be merged tomorrow morning.
> > > > > > > It would be nice if other community members reviewed my changes
> > in
> > > > > > > ignite-950-new branch before it gets to master.
> > > > > > >
> > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > [hidden email]
> > > > >:
> > > > > > >
> > > > > > > > Thanks Vladislav!
> > > > > > > >
> > > > > > > > Would also be nice to get an update from other committers
> > > involved
> > > > in
> > > > > > the
> > > > > > > > outlined tickets. Specifically whether the ticket has been
> > merged
> > > > to
> > > > > > > master
> > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > D.
> > > > > > > >
> > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > [hidden email]>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > Vladislav,
> > > > > > any
> > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > >
> > > > > > > > > I will have it done by thursday.
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > > Vladisav
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <[hidden email]
> >
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Can/will this include
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > ?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I don’t see why not. Would be nice if one of the
> committers
> > > > could
> > > > > > > pick
> > > > > > > > up
> > > > > > > > > > the review for this patch.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > [hidden email]
> > > > > > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > [hidden email]
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > release
> > > > > which
> > > > > > > > will
> > > > > > > > > > > > include
> > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> query
> > > > > > > > non-collocated
> > > > > > > > > > > data
> > > > > > > > > > > > as
> > > > > > > > > > > > >> well
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > optimizations
> > > > > > > - I
> > > > > > > > > > will
> > > > > > > > > > > > >> merge
> > > > > > > > > > > > >> these changes from 'ignite-1.4-slow-server-debug'
> > > today
> > > > or
> > > > > > > > > tomorrow.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> 10. I would also like to include distributed
> > > Semaphore.
> > > > > > > > Vladislav,
> > > > > > > > > > any
> > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > >> <https://issues.apache.org/jira/browse/IGNITE-426
> > >638
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp. assignees
> of
> > > > > > mentioned
> > > > > > > > > > issues,
> > > > > > > > > > > > >> please respond to this email and let us know when
> > can
> > > we
> > > > > > > expect
> > > > > > > > > your
> > > > > > > > > > > > >> changes being merged to master and release branch?
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > >>
> > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > >>
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>



--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Vladimir Ozerov
Igniters, here is curernt status of platform/portable tickets.

As I understand, IGNITE-950 is almost ready and will be merged very soon.
There are 5 more tickets which depends on it:

*IGNITE-1845*, *IGNITE-1846* - move portable API changes to .Net and C++.
This is a matter of refacotring, should not be a problem.
*IGNITE-1819* - remove "metadata enabled" flag. Also fairly simple ticket.
*IGNITE-1847* - move "field" method from PortableObject to
PortableMetadata. Also should be trivial.
*IGNITE-1816* - optionaly do not write field IDs to footer. Important
ticket, I'm working on it. About ~50% ready.

All in all, none of these tickets are showstoppers for merge of
IGNITE-950/IGNITE-1282 to release branch.

Also I measured query performance on some local benchmarks and got
acceptable resutls - queries are about 5-7% slower with poratbles than with
OptimizedMarshaller. Looks very promising to me provided that we work with
deserialized objects now.


On Wed, Nov 4, 2015 at 1:50 AM, Alexey Kuznetsov <[hidden email]>
wrote:

> I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
> https://issues.apache.org/jira/browse/IGNITE-1753).
> Issue is implemented and waiting for  IGNITE-950 to be merged into
> ignite-1282.
>
> On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > Good news for the IGNITE-950 ticket - CI looks good, changes will be
> merged
> > to ignite-1282 integration branch after benchmarks re-run.
> >
> > 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <[hidden email]>:
> >
> > > I implemented changes related to IGNITE-426 task. Currently
> investigating
> > > performance degradation for atomic caches. I expect the ticket to be
> > merged
> > > in 2 days.
> > >
> > > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > > [hidden email]
> > > > wrote:
> > >
> > > > IGNITE-950 is taking more time to be merged than I originally
> > estimated.
> > > We
> > > > had a couple of silly bugs, such as loosing cache operation context
> on
> > > > async cache operations, which led to hard-to debug failures in the
> > > platform
> > > > integration code.
> > > > I also added some sanity checks to indexing and found that I ran
> > > benchmarks
> > > > for new binary format on a model with externalizable classes, so the
> > > result
> > > > I've got were invalid, need more time to fix the model and re-run
> > > > benchmarks.
> > > >
> > > > I am currently waiting for another CI run, will give an update in
> > several
> > > > hours.
> > > >
> > > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> > > >
> > > > > Here are my current status for all interop-related stuff (you can
> > view
> > > > > these tickets using query "project = IGNITE AND status in (Open,
> "In
> > > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > > interop
> > > > > AND fixVersion = 1.5"):
> > > > >
> > > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > > Ready. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > > footer.*
> > > > > Not started yet.
> > > > >
> > > > > + Several minor tickets.
> > > > >
> > > > > All in all, I expect all these tickets to be ready in 2 days.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > > [hidden email]
> > > > > > wrote:
> > > > >
> > > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > > *ticket*".
> > > > > The
> > > > > > changes are in ignite-950-new branch because it is a result of
> work
> > > on
> > > > > > multiple sub-tickets and it is currently used as an integration
> > > branch.
> > > > > >
> > > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <
> [hidden email]
> > >:
> > > > > >
> > > > > > > Alexey,
> > > > > > >
> > > > > > > I am confused. Why do you have 2 branches?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > > [hidden email]
> > > > > > > > wrote:
> > > > > > >
> > > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> > Currently
> > > > the
> > > > > > API
> > > > > > > > changes are finished and now I am mostly fixing the CI tests.
> > In
> > > > > fact,
> > > > > > I
> > > > > > > > just submitted the latest fix related to the new .NET
> platform
> > > > > > > > functionality and hope CI tests will pass, in this case it
> will
> > > be
> > > > > > ready
> > > > > > > to
> > > > > > > > be merged tomorrow morning.
> > > > > > > > It would be nice if other community members reviewed my
> changes
> > > in
> > > > > > > > ignite-950-new branch before it gets to master.
> > > > > > > >
> > > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > > [hidden email]
> > > > > >:
> > > > > > > >
> > > > > > > > > Thanks Vladislav!
> > > > > > > > >
> > > > > > > > > Would also be nice to get an update from other committers
> > > > involved
> > > > > in
> > > > > > > the
> > > > > > > > > outlined tickets. Specifically whether the ticket has been
> > > merged
> > > > > to
> > > > > > > > master
> > > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > > [hidden email]>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >
> > > > > > > > > > I will have it done by thursday.
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Vladisav
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <
> [hidden email]
> > >
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can/will this include
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > > ?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I don’t see why not. Would be nice if one of the
> > committers
> > > > > could
> > > > > > > > pick
> > > > > > > > > up
> > > > > > > > > > > the review for this patch.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > > [hidden email]
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > > [hidden email]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > > [hidden email]
> > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > > release
> > > > > > which
> > > > > > > > > will
> > > > > > > > > > > > > include
> > > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> > query
> > > > > > > > > non-collocated
> > > > > > > > > > > > data
> > > > > > > > > > > > > as
> > > > > > > > > > > > > >> well
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > > optimizations
> > > > > > > > - I
> > > > > > > > > > > will
> > > > > > > > > > > > > >> merge
> > > > > > > > > > > > > >> these changes from
> 'ignite-1.4-slow-server-debug'
> > > > today
> > > > > or
> > > > > > > > > > tomorrow.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 10. I would also like to include distributed
> > > > Semaphore.
> > > > > > > > > Vladislav,
> > > > > > > > > > > any
> > > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > > >> <
> https://issues.apache.org/jira/browse/IGNITE-426
> > > >638
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp.
> assignees
> > of
> > > > > > > mentioned
> > > > > > > > > > > issues,
> > > > > > > > > > > > > >> please respond to this email and let us know
> when
> > > can
> > > > we
> > > > > > > > expect
> > > > > > > > > > your
> > > > > > > > > > > > > >> changes being merged to master and release
> branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

Alexey Goncharuk
In reply to this post by Alexey Kuznetsov-2
Folks,

It looks like Ignite-950 branch is ready to be merged to ignite-1282. Can
someone pull latest changes from 1.5 to ignite-1282 branch? I know some of
the critical issues have been fixed lately, so I would like to give CI
another run before my merge.

2015-11-04 1:50 GMT+03:00 Alexey Kuznetsov <[hidden email]>:

> I'm working on IGNITE-1753 Rework CacheJdbcPojoStore to new API (
> https://issues.apache.org/jira/browse/IGNITE-1753).
> Issue is implemented and waiting for  IGNITE-950 to be merged into
> ignite-1282.
>
> On Wed, Nov 4, 2015 at 5:22 AM, Alexey Goncharuk <
> [hidden email]
> > wrote:
>
> > Good news for the IGNITE-950 ticket - CI looks good, changes will be
> merged
> > to ignite-1282 integration branch after benchmarks re-run.
> >
> > 2015-11-03 21:37 GMT+03:00 Nikolay Tikhonov <[hidden email]>:
> >
> > > I implemented changes related to IGNITE-426 task. Currently
> investigating
> > > performance degradation for atomic caches. I expect the ticket to be
> > merged
> > > in 2 days.
> > >
> > > On Tue, Nov 3, 2015 at 6:47 PM, Alexey Goncharuk <
> > > [hidden email]
> > > > wrote:
> > >
> > > > IGNITE-950 is taking more time to be merged than I originally
> > estimated.
> > > We
> > > > had a couple of silly bugs, such as loosing cache operation context
> on
> > > > async cache operations, which led to hard-to debug failures in the
> > > platform
> > > > integration code.
> > > > I also added some sanity checks to indexing and found that I ran
> > > benchmarks
> > > > for new binary format on a model with externalizable classes, so the
> > > result
> > > > I've got were invalid, need more time to fix the model and re-run
> > > > benchmarks.
> > > >
> > > > I am currently waiting for another CI run, will give an update in
> > several
> > > > hours.
> > > >
> > > > 2015-11-03 17:51 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> > > >
> > > > > Here are my current status for all interop-related stuff (you can
> > view
> > > > > these tickets using query "project = IGNITE AND status in (Open,
> "In
> > > > > Progress", Reopened, Resolved, "Patch Available") AND component =
> > > interop
> > > > > AND fixVersion = 1.5"):
> > > > >
> > > > > *IGNITE-1819 - Remove metadataEnabled flag in Java*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1845, IGNITE-1846 - portable API renamings in CPP and .Net*
> > > > > Trivial. Waiting for IGNITE-950 merge.
> > > > >
> > > > > *IGNITE-1803 - Optimized field lookup for queries*
> > > > > Ready. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1847 - Add "field" method to portable metadata.*
> > > > > Not started yet. Waiting for IGNITE-950 to merge.
> > > > >
> > > > > *IGNITE-1816 - Optionally do not write field IDs to portable object
> > > > > footer.*
> > > > > Not started yet.
> > > > >
> > > > > + Several minor tickets.
> > > > >
> > > > > All in all, I expect all these tickets to be ready in 2 days.
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Nov 3, 2015 at 1:43 AM, Alexey Goncharuk <
> > > > > [hidden email]
> > > > > > wrote:
> > > > >
> > > > > > I'm sorry, I meant to write "changes related to IGNITE-1486
> > > *ticket*".
> > > > > The
> > > > > > changes are in ignite-950-new branch because it is a result of
> work
> > > on
> > > > > > multiple sub-tickets and it is currently used as an integration
> > > branch.
> > > > > >
> > > > > > 2015-11-03 1:39 GMT+03:00 Dmitriy Setrakyan <
> [hidden email]
> > >:
> > > > > >
> > > > > > > Alexey,
> > > > > > >
> > > > > > > I am confused. Why do you have 2 branches?
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Mon, Nov 2, 2015 at 2:32 PM, Alexey Goncharuk <
> > > > > > > [hidden email]
> > > > > > > > wrote:
> > > > > > >
> > > > > > > > I am finalizing changes related to IGNITE-1486 branch.
> > Currently
> > > > the
> > > > > > API
> > > > > > > > changes are finished and now I am mostly fixing the CI tests.
> > In
> > > > > fact,
> > > > > > I
> > > > > > > > just submitted the latest fix related to the new .NET
> platform
> > > > > > > > functionality and hope CI tests will pass, in this case it
> will
> > > be
> > > > > > ready
> > > > > > > to
> > > > > > > > be merged tomorrow morning.
> > > > > > > > It would be nice if other community members reviewed my
> changes
> > > in
> > > > > > > > ignite-950-new branch before it gets to master.
> > > > > > > >
> > > > > > > > 2015-11-02 22:27 GMT+03:00 Dmitriy Setrakyan <
> > > > [hidden email]
> > > > > >:
> > > > > > > >
> > > > > > > > > Thanks Vladislav!
> > > > > > > > >
> > > > > > > > > Would also be nice to get an update from other committers
> > > > involved
> > > > > in
> > > > > > > the
> > > > > > > > > outlined tickets. Specifically whether the ticket has been
> > > merged
> > > > > to
> > > > > > > > master
> > > > > > > > > or not, and if not, what should be the expectation.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Nov 2, 2015 at 11:23 AM, Vladisav Jelisavcic <
> > > > > > > > [hidden email]>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > >10. I would also like to include distributed Semaphore.
> > > > > Vladislav,
> > > > > > > any
> > > > > > > > > > >chance you can finish with it this week?
> > > > > > > > > > >https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > ><https://issues.apache.org/jira/browse/IGNITE-426>638
> > > > > > > > > >
> > > > > > > > > > I will have it done by thursday.
> > > > > > > > > >
> > > > > > > > > > Best regards,
> > > > > > > > > > Vladisav
> > > > > > > > > >
> > > > > > > > > > On Mon, Nov 2, 2015 at 6:40 PM, Dmitriy Setrakyan <
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > On Mon, Nov 2, 2015 at 6:58 AM, M G <
> [hidden email]
> > >
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can/will this include
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-1681
> > > > > > > > > > > ?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I don’t see why not. Would be nice if one of the
> > committers
> > > > > could
> > > > > > > > pick
> > > > > > > > > up
> > > > > > > > > > > the review for this patch.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Nov 2, 2015 at 1:51 PM, Anton Vinogradov <
> > > > > > > > > > > [hidden email]
> > > > > > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Branch ignite-1.5 created.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:39 PM, Anton Vinogradov <
> > > > > > > > > > > > [hidden email]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > I assume that correct link at 10th feature is
> > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-638
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Nov 2, 2015 at 4:35 PM, Yakov Zhdanov <
> > > > > > > > > [hidden email]
> > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> Guys,
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> I think we can start preparation to Ignite-1.5
> > > release
> > > > > > which
> > > > > > > > > will
> > > > > > > > > > > > > include
> > > > > > > > > > > > > >> many interesting features:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 1. Portable object API
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1486
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 2. Ignite.NET and Ignite C++
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1282
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 3. Optimistic serializable transactions
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1607
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 4. Distributed SQL joins - we will be able to
> > query
> > > > > > > > > non-collocated
> > > > > > > > > > > > data
> > > > > > > > > > > > > as
> > > > > > > > > > > > > >> well
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1232
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 5. Enhanced Oracle and IBM JDK interoperability
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-1526
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 6. MQTT streamer
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-535
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 7. Continuous query failover
> > > > > > > > > > > > > >>
> https://issues.apache.org/jira/browse/IGNITE-426
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 8. Significant transactional cache performance
> > > > > > optimizations
> > > > > > > > - I
> > > > > > > > > > > will
> > > > > > > > > > > > > >> merge
> > > > > > > > > > > > > >> these changes from
> 'ignite-1.4-slow-server-debug'
> > > > today
> > > > > or
> > > > > > > > > > tomorrow.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 9. Many stability and fault-tolerance fixes.
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> 10. I would also like to include distributed
> > > > Semaphore.
> > > > > > > > > Vladislav,
> > > > > > > > > > > any
> > > > > > > > > > > > > >> chance you can finish with it this week?
> > > > > > > > > > > > > >> https://issues.apache.org/jira/browse/IGNITE-
> > > > > > > > > > > > > >> <
> https://issues.apache.org/jira/browse/IGNITE-426
> > > >638
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Thanks to everyone involved! Guys, esp.
> assignees
> > of
> > > > > > > mentioned
> > > > > > > > > > > issues,
> > > > > > > > > > > > > >> please respond to this email and let us know
> when
> > > can
> > > > we
> > > > > > > > expect
> > > > > > > > > > your
> > > > > > > > > > > > > >> changes being merged to master and release
> branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Can someone create ignite-1.5 release branch?
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> --Yakov
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite-1.5 Release

dsetrakyan
In reply to this post by Vladimir Ozerov
On Wed, Nov 4, 2015 at 10:25 AM, Vladimir Ozerov <[hidden email]>
wrote:

>
> Also I measured query performance on some local benchmarks and got
> acceptable resutls - queries are about 5-7% slower with poratbles than with
> OptimizedMarshaller. Looks very promising to me provided that we work with
> deserialized objects now.


Vladimir, I don’t think we can treat these results as acceptable. So far,
Ignite has been doing very well on all competitive benchmarks, and we
cannot afford to start loosing any of them.

Now, I remember seeing emails about many more performance optimizations we
can add, like aligning String representation with binary representation,
etc. Do you think after adding all the optimizations we will still be
slower or faster?

D.
1234 ... 6