Apache Ignite Developers - Legacy Mail Archive

Apache Ignite 2.0 Release

Classic

List

Threaded

48 messages Options

123

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

Folks,

I would also encourage you to review all 2,0 tickets that are either
assigned to you or submitted by you and move them to the next version (2.1)
if you cannot complete them in the nearest time. Currently we have 554
opened tickets for 2.0. Let's make sure that we have about several dozens
in the nearest time.

Thank you.

On Thu, Apr 6, 2017 at 12:58 PM, Вадим Опольский <[hidden email]>
wrote:

> Hello community!
>
> Denis, issue IGNITE-1794
> <https://issues.apache.org/jira/browse/IGNITE-1794> - Hibernate 5 Support
> has been ready for review from 24 March.
>
> The tests in Team City executed successfully.
>
> Vadim Opolski
>
> 2017-04-06 5:04 GMT+03:00 Denis Magda <[hidden email]>:
>
> > *Denis Magda:*
> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
> Provide
> > integration with Spring Data
> >
> >
> > Will be finished and merged by the code freeze date. I’m on a business
> > trip now and don’t have extra time to complete the feature.
> >
> > Plus, following your template these are additional tickets:
> >
> > *Alexey Kuznetsov*
> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> Discontinue
> > the schema-import utility
> >
> > *Sergey Chugunov*
> > IGNITE-4536 <https://issues.apache.org/jira/browse/IGNITE-4536> - Update
> > metrics for new offheap storage
> >
> > *Nikita Ivanov*
> > IGNITE-4572 <https://issues.apache.org/jira/browse/IGNITE-4572> -
> Machine
> > Learning: Develop distributed algebra support for dense and sparse data
> > sets.
> >
> > *Roman Shtykh*
> > IGNITE-4539 <https://issues.apache.org/jira/browse/IGNITE-4539> -
> > RocketMQ Data Streamer
> >
> > *Vadim Opolski*
> > IGNITE-1794 <https://issues.apache.org/jira/browse/IGNITE-1794> -
> > Hibernate 5 Support
> >
> > —
> > Denis
> >
> > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <[hidden email]>
> > wrote:
> >
> > Guys,
> >
> > Please provide a status underneath every ticket listed below, so we can
> get
> > a full picture in one email thread:
> >
> > *Alexey Goncharuk:*
> > IGNITE-3477 <https://issues.apache.org/jira/browse/IGNITE-3477> - Rework
> > offheap storage
> > IGNITE-4337 <https://issues.apache.org/jira/browse/IGNITE-4337> -
> > Introduce
> > persistence interface to allow build reliable persistence plugins
> >
> > *Alexander Menshikov:*
> > IGNITE-4699 <https://issues.apache.org/jira/browse/IGNITE-4699> -
> > Introduce
> > custom configurable executors.
> >
> > *Denis Magda:*
> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
> Provide
> > integration with Spring Data
> >
> > *Dmitriy Karachentsev:*
> > IGNITE-4477 <https://issues.apache.org/jira/browse/IGNITE-4477> - Fix
> > IgniteFuture.listen() and IgniteFuture.chain() semantics
> >
> > *Ilya Lantukh:*
> > IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535>
> > <https://issues.apache.org/jira/browse/IGNITE-4535>- Add option to store
> > deserialized values on-heap
> >
> > *Ivan Rakov:*
> > IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> -
> > Implement
> > offheap eviction policies based on page memory
> >
> > *Sergey Kalashnikov:*
> > IGNITE-3595 <https://issues.apache.org/jira/browse/IGNITE-3595> -
> Improve
> > Enum fields handling in SQL.
> >
> > *Sergi Vladykin:*
> > IGNITE-3869 <https://issues.apache.org/jira/browse/IGNITE-3869> - Reduce
> > number of temporary objects produced by H2
> >
> > *Taras Ledkov:*
> > IGNITE-3469 <https://issues.apache.org/jira/browse/IGNITE-3469> - Get
> rid
> > of deprecated APIs and entities
> >
> > *Vladimir Ozerov:*
> > IGNITE-4565 <https://issues.apache.org/jira/browse/IGNITE-4565> -
> Support
> > CREATE INDEX DDL statements
> >
> > *Yakov Zdanov:*
> > IGNITE-4799 <https://issues.apache.org/jira/browse/IGNITE-4799> - Remove
> > TcpDiscoverySpi.heartbeatsFrequency parameter
> >
> >
> > *Denis*, we still have 5 issues that are *unassigned*. Are they supposed
> to
> > be getting into release?
> >
> > IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488> -
> Prohibit
> > null as name in all the components (cache name first of all).
> > IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596> - Hadoop
> > edition can't be compiled against spark 2.0.0
> > IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794> -
> > Reconsider
> > CachePeekMode.ONHEAP
> > IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202> - Local
> > server query result doesn't include versions in entries
> > IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398> - .NET:
> > Change default mapper behavior
> >
> >
> > D.
> >
> > On Wed, Apr 5, 2017 at 6:07 PM, Denis Magda <[hidden email]> wrote:
> >
> > Dmitriy,
> >
> > You can find all the required tickets with contributors assigned here:
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
> > ApacheIgnite2.0-Requiredtickets <https://cwiki.apache.org/
> > confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-
> > Requiredtickets>
> >
> > In short, Alex G., Sergi, Vovan, Taras, Yakov, Sam, etc. (almost all the
> > community) please share your readiness with the rest of the community.
> >
> > —
> > Denis
> >
> > On Apr 5, 2017, at 9:03 PM, Dmitriy Setrakyan <[hidden email]>
> >
> > wrote:
> >
> >
> > Denis,
> >
> > I think it will be worth while to list all the tickets by status together
> > with a name of the engineer assigned to it. This way most folks involved
> > would provide a response sooner.
> >
> > What do you think?
> >
> > D.
> >
> > On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda <[hidden email]> wrote:
> >
> > Igniters,
> >
> > What’s the overall status of 2.0 release? I see that many tickets
> >
> > related
> >
> > to the page memory [1] are still in the open state and, looks like, this
> > new memory architecture has not been fully merged yet. In addition, a
> >
> > new
> >
> > version of H2 has to be released prior to 2.0.
> >
> > All this threatens the release schedule we agreed on. According to the
> > plan the next week is a week of code freeze:
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
> > ApacheIgnite2.0-Releasephases <https://cwiki.apache.org/
> > confluence/display/IGNITE/Apache+Ignite+2.0#
> >
> > ApacheIgnite2.0-Releasephases>
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-3477 <
> > https://issues.apache.org/jira/browse/IGNITE-3477>
> >
> > —
> > Denis
> >
> > On Mar 31, 2017, at 4:02 AM, Vladimir Ozerov <[hidden email]>
> >
> > wrote:
> >
> >
> > Another big merge - now almost all our setters on public configuration
> > return "this" instance to allow for convenient chaining [1]. Big
> > thanks to *Andrew
> > Mashenkov* for making this happen.
> > Ideally I would also try to replace "set(Collection<Something>)" with "
> > set(Something...)". This should make configuration even more easier.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-4564
> >
> > On Fri, Mar 31, 2017 at 2:18 AM, Denis Magda <[hidden email]>
> >
> > wrote:
> >
> >
> > Vovan,
> >
> > I expect to finalize and merge Spring Data Integration by the code
> >
> > freeze
> >
> > time (April 14th):
> > IGNITE-1192Provide integration with Spring Data <
> > https://issues.apache.org/jira/browse/IGNITE-1192>
> >
> > —
> > Denis
> >
> > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov <[hidden email]>
> >
> > wrote:
> >
> >
> > Igniters,
> >
> > We are getting closer to proposed code freeze date. Could you please
> >
> > go
> >
> > through the list of required [1] tickets and provide brief update on
> >
> > where
> >
> > we are?
> >
> > As per myself, I am curerntly working on CREATE/DROP index feature
> > stabilization and expect it to be ready for review on the next week.
> >
> > Vladimir.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> >
> > Apache+Ignite+2.0
> >
> >
> > On Tue, Mar 28, 2017 at 9:11 PM, nivanov <[hidden email]>
> >
> > wrote:
> >
> >
> > I think we can make it on time to add IgniteML (a.k.a. distributed
> >
> > math) to
> >
> > 2.0 release pipeline.
> >
> >
> >
> > --
> > View this message in context: http://apache-ignite-
> > developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-
> > tp15690p15857.html
> > Sent from the Apache Ignite Developers mailing list archive at
> >
> > Nabble.com.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

Convenient filter to view your tickets (you must be logged in to JIRA):
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.0%20AND%20resolution%20%3D%20Unresolved%20AND%20(assignee%20%3D%20currentUser()%20OR%20reporter%20%3D%20currentUser())%20ORDER%20BY%20created%20ASC

On Thu, Apr 6, 2017 at 1:34 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Folks,
>
> I would also encourage you to review all 2,0 tickets that are either
> assigned to you or submitted by you and move them to the next version (2.1)
> if you cannot complete them in the nearest time. Currently we have 554
> opened tickets for 2.0. Let's make sure that we have about several dozens
> in the nearest time.
>
> Thank you.
>
> On Thu, Apr 6, 2017 at 12:58 PM, Вадим Опольский <[hidden email]>
> wrote:
>
>> Hello community!
>>
>> Denis, issue IGNITE-1794
>> <https://issues.apache.org/jira/browse/IGNITE-1794> - Hibernate 5 Support
>> has been ready for review from 24 March.
>>
>> The tests in Team City executed successfully.
>>
>> Vadim Opolski
>>
>> 2017-04-06 5:04 GMT+03:00 Denis Magda <[hidden email]>:
>>
>> > *Denis Magda:*
>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
>> Provide
>> > integration with Spring Data
>> >
>> >
>> > Will be finished and merged by the code freeze date. I’m on a business
>> > trip now and don’t have extra time to complete the feature.
>> >
>> > Plus, following your template these are additional tickets:
>> >
>> > *Alexey Kuznetsov*
>> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
>> Discontinue
>> > the schema-import utility
>> >
>> > *Sergey Chugunov*
>> > IGNITE-4536 <https://issues.apache.org/jira/browse/IGNITE-4536> -
>> Update
>> > metrics for new offheap storage
>> >
>> > *Nikita Ivanov*
>> > IGNITE-4572 <https://issues.apache.org/jira/browse/IGNITE-4572> -
>> Machine
>> > Learning: Develop distributed algebra support for dense and sparse data
>> > sets.
>> >
>> > *Roman Shtykh*
>> > IGNITE-4539 <https://issues.apache.org/jira/browse/IGNITE-4539> -
>> > RocketMQ Data Streamer
>> >
>> > *Vadim Opolski*
>> > IGNITE-1794 <https://issues.apache.org/jira/browse/IGNITE-1794> -
>> > Hibernate 5 Support
>> >
>> > —
>> > Denis
>> >
>> > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <[hidden email]>
>> > wrote:
>> >
>> > Guys,
>> >
>> > Please provide a status underneath every ticket listed below, so we can
>> get
>> > a full picture in one email thread:
>> >
>> > *Alexey Goncharuk:*
>> > IGNITE-3477 <https://issues.apache.org/jira/browse/IGNITE-3477> -
>> Rework
>> > offheap storage
>> > IGNITE-4337 <https://issues.apache.org/jira/browse/IGNITE-4337> -
>> > Introduce
>> > persistence interface to allow build reliable persistence plugins
>> >
>> > *Alexander Menshikov:*
>> > IGNITE-4699 <https://issues.apache.org/jira/browse/IGNITE-4699> -
>> > Introduce
>> > custom configurable executors.
>> >
>> > *Denis Magda:*
>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
>> Provide
>> > integration with Spring Data
>> >
>> > *Dmitriy Karachentsev:*
>> > IGNITE-4477 <https://issues.apache.org/jira/browse/IGNITE-4477> - Fix
>> > IgniteFuture.listen() and IgniteFuture.chain() semantics
>> >
>> > *Ilya Lantukh:*
>> > IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535>
>> > <https://issues.apache.org/jira/browse/IGNITE-4535>- Add option to
>> store
>> > deserialized values on-heap
>> >
>> > *Ivan Rakov:*
>> > IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> -
>> > Implement
>> > offheap eviction policies based on page memory
>> >
>> > *Sergey Kalashnikov:*
>> > IGNITE-3595 <https://issues.apache.org/jira/browse/IGNITE-3595> -
>> Improve
>> > Enum fields handling in SQL.
>> >
>> > *Sergi Vladykin:*
>> > IGNITE-3869 <https://issues.apache.org/jira/browse/IGNITE-3869> -
>> Reduce
>> > number of temporary objects produced by H2
>> >
>> > *Taras Ledkov:*
>> > IGNITE-3469 <https://issues.apache.org/jira/browse/IGNITE-3469> - Get
>> rid
>> > of deprecated APIs and entities
>> >
>> > *Vladimir Ozerov:*
>> > IGNITE-4565 <https://issues.apache.org/jira/browse/IGNITE-4565> -
>> Support
>> > CREATE INDEX DDL statements
>> >
>> > *Yakov Zdanov:*
>> > IGNITE-4799 <https://issues.apache.org/jira/browse/IGNITE-4799> -
>> Remove
>> > TcpDiscoverySpi.heartbeatsFrequency parameter
>> >
>> >
>> > *Denis*, we still have 5 issues that are *unassigned*. Are they
>> supposed to
>> > be getting into release?
>> >
>> > IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488> -
>> Prohibit
>> > null as name in all the components (cache name first of all).
>> > IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596> -
>> Hadoop
>> > edition can't be compiled against spark 2.0.0
>> > IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794> -
>> > Reconsider
>> > CachePeekMode.ONHEAP
>> > IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202> - Local
>> > server query result doesn't include versions in entries
>> > IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398> - .NET:
>> > Change default mapper behavior
>> >
>> >
>> > D.
>> >
>> > On Wed, Apr 5, 2017 at 6:07 PM, Denis Magda <[hidden email]> wrote:
>> >
>> > Dmitriy,
>> >
>> > You can find all the required tickets with contributors assigned here:
>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
>> > ApacheIgnite2.0-Requiredtickets <https://cwiki.apache.org/
>> > confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-
>> > Requiredtickets>
>> >
>> > In short, Alex G., Sergi, Vovan, Taras, Yakov, Sam, etc. (almost all the
>> > community) please share your readiness with the rest of the community.
>> >
>> > —
>> > Denis
>> >
>> > On Apr 5, 2017, at 9:03 PM, Dmitriy Setrakyan <[hidden email]>
>> >
>> > wrote:
>> >
>> >
>> > Denis,
>> >
>> > I think it will be worth while to list all the tickets by status
>> together
>> > with a name of the engineer assigned to it. This way most folks involved
>> > would provide a response sooner.
>> >
>> > What do you think?
>> >
>> > D.
>> >
>> > On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda <[hidden email]> wrote:
>> >
>> > Igniters,
>> >
>> > What’s the overall status of 2.0 release? I see that many tickets
>> >
>> > related
>> >
>> > to the page memory [1] are still in the open state and, looks like, this
>> > new memory architecture has not been fully merged yet. In addition, a
>> >
>> > new
>> >
>> > version of H2 has to be released prior to 2.0.
>> >
>> > All this threatens the release schedule we agreed on. According to the
>> > plan the next week is a week of code freeze:
>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
>> > ApacheIgnite2.0-Releasephases <https://cwiki.apache.org/
>> > confluence/display/IGNITE/Apache+Ignite+2.0#
>> >
>> > ApacheIgnite2.0-Releasephases>
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-3477 <
>> > https://issues.apache.org/jira/browse/IGNITE-3477>
>> >
>> > —
>> > Denis
>> >
>> > On Mar 31, 2017, at 4:02 AM, Vladimir Ozerov <[hidden email]>
>> >
>> > wrote:
>> >
>> >
>> > Another big merge - now almost all our setters on public configuration
>> > return "this" instance to allow for convenient chaining [1]. Big
>> > thanks to *Andrew
>> > Mashenkov* for making this happen.
>> > Ideally I would also try to replace "set(Collection<Something>)" with "
>> > set(Something...)". This should make configuration even more easier.
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-4564
>> >
>> > On Fri, Mar 31, 2017 at 2:18 AM, Denis Magda <[hidden email]>
>> >
>> > wrote:
>> >
>> >
>> > Vovan,
>> >
>> > I expect to finalize and merge Spring Data Integration by the code
>> >
>> > freeze
>> >
>> > time (April 14th):
>> > IGNITE-1192Provide integration with Spring Data <
>> > https://issues.apache.org/jira/browse/IGNITE-1192>
>> >
>> > —
>> > Denis
>> >
>> > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov <[hidden email]>
>> >
>> > wrote:
>> >
>> >
>> > Igniters,
>> >
>> > We are getting closer to proposed code freeze date. Could you please
>> >
>> > go
>> >
>> > through the list of required [1] tickets and provide brief update on
>> >
>> > where
>> >
>> > we are?
>> >
>> > As per myself, I am curerntly working on CREATE/DROP index feature
>> > stabilization and expect it to be ready for review on the next week.
>> >
>> > Vladimir.
>> >
>> > [1] https://cwiki.apache.org/confluence/display/IGNITE/
>> >
>> > Apache+Ignite+2.0
>> >
>> >
>> > On Tue, Mar 28, 2017 at 9:11 PM, nivanov <[hidden email]>
>> >
>> > wrote:
>> >
>> >
>> > I think we can make it on time to add IgniteML (a.k.a. distributed
>> >
>> > math) to
>> >
>> > 2.0 release pipeline.
>> >
>> >
>> >
>> > --
>> > View this message in context: http://apache-ignite-
>> > developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-
>> > tp15690p15857.html
>> > Sent from the Apache Ignite Developers mailing list archive at
>> >
>> > Nabble.com.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

I am almost done with DDL. It will be available for review in the nearest
time.

On Thu, Apr 6, 2017 at 1:38 PM, Vladimir Ozerov <[hidden email]>
wrote:

> Convenient filter to view your tickets (you must be logged in to JIRA):
> <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> 20fixVersion%20%3D%202.0%20AND%20resolution%20%3D%20Unresolved%20AND%20(
> assignee%20%3D%20currentUser()%20OR%20reporter%20%3D%
> 20currentUser())%20ORDER%20BY%20created%20ASC
>
> On Thu, Apr 6, 2017 at 1:34 PM, Vladimir Ozerov <[hidden email]>
> wrote:
>
>> Folks,
>>
>> I would also encourage you to review all 2,0 tickets that are either
>> assigned to you or submitted by you and move them to the next version (2.1)
>> if you cannot complete them in the nearest time. Currently we have 554
>> opened tickets for 2.0. Let's make sure that we have about several dozens
>> in the nearest time.
>>
>> Thank you.
>>
>> On Thu, Apr 6, 2017 at 12:58 PM, Вадим Опольский <[hidden email]>
>> wrote:
>>
>>> Hello community!
>>>
>>> Denis, issue IGNITE-1794
>>> <https://issues.apache.org/jira/browse/IGNITE-1794> - Hibernate 5
>>> Support
>>> has been ready for review from 24 March.
>>>
>>> The tests in Team City executed successfully.
>>>
>>> Vadim Opolski
>>>
>>> 2017-04-06 5:04 GMT+03:00 Denis Magda <[hidden email]>:
>>>
>>> > *Denis Magda:*
>>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
>>> Provide
>>> > integration with Spring Data
>>> >
>>> >
>>> > Will be finished and merged by the code freeze date. I’m on a business
>>> > trip now and don’t have extra time to complete the feature.
>>> >
>>> > Plus, following your template these are additional tickets:
>>> >
>>> > *Alexey Kuznetsov*
>>> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
>>> Discontinue
>>> > the schema-import utility
>>> >
>>> > *Sergey Chugunov*
>>> > IGNITE-4536 <https://issues.apache.org/jira/browse/IGNITE-4536> -
>>> Update
>>> > metrics for new offheap storage
>>> >
>>> > *Nikita Ivanov*
>>> > IGNITE-4572 <https://issues.apache.org/jira/browse/IGNITE-4572> -
>>> Machine
>>> > Learning: Develop distributed algebra support for dense and sparse data
>>> > sets.
>>> >
>>> > *Roman Shtykh*
>>> > IGNITE-4539 <https://issues.apache.org/jira/browse/IGNITE-4539> -
>>> > RocketMQ Data Streamer
>>> >
>>> > *Vadim Opolski*
>>> > IGNITE-1794 <https://issues.apache.org/jira/browse/IGNITE-1794> -
>>> > Hibernate 5 Support
>>> >
>>> > —
>>> > Denis
>>> >
>>> > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <[hidden email]>
>>> > wrote:
>>> >
>>> > Guys,
>>> >
>>> > Please provide a status underneath every ticket listed below, so we
>>> can get
>>> > a full picture in one email thread:
>>> >
>>> > *Alexey Goncharuk:*
>>> > IGNITE-3477 <https://issues.apache.org/jira/browse/IGNITE-3477> -
>>> Rework
>>> > offheap storage
>>> > IGNITE-4337 <https://issues.apache.org/jira/browse/IGNITE-4337> -
>>> > Introduce
>>> > persistence interface to allow build reliable persistence plugins
>>> >
>>> > *Alexander Menshikov:*
>>> > IGNITE-4699 <https://issues.apache.org/jira/browse/IGNITE-4699> -
>>> > Introduce
>>> > custom configurable executors.
>>> >
>>> > *Denis Magda:*
>>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
>>> Provide
>>> > integration with Spring Data
>>> >
>>> > *Dmitriy Karachentsev:*
>>> > IGNITE-4477 <https://issues.apache.org/jira/browse/IGNITE-4477> - Fix
>>> > IgniteFuture.listen() and IgniteFuture.chain() semantics
>>> >
>>> > *Ilya Lantukh:*
>>> > IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535>
>>> > <https://issues.apache.org/jira/browse/IGNITE-4535>- Add option to
>>> store
>>> > deserialized values on-heap
>>> >
>>> > *Ivan Rakov:*
>>> > IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> -
>>> > Implement
>>> > offheap eviction policies based on page memory
>>> >
>>> > *Sergey Kalashnikov:*
>>> > IGNITE-3595 <https://issues.apache.org/jira/browse/IGNITE-3595> -
>>> Improve
>>> > Enum fields handling in SQL.
>>> >
>>> > *Sergi Vladykin:*
>>> > IGNITE-3869 <https://issues.apache.org/jira/browse/IGNITE-3869> -
>>> Reduce
>>> > number of temporary objects produced by H2
>>> >
>>> > *Taras Ledkov:*
>>> > IGNITE-3469 <https://issues.apache.org/jira/browse/IGNITE-3469> - Get
>>> rid
>>> > of deprecated APIs and entities
>>> >
>>> > *Vladimir Ozerov:*
>>> > IGNITE-4565 <https://issues.apache.org/jira/browse/IGNITE-4565> -
>>> Support
>>> > CREATE INDEX DDL statements
>>> >
>>> > *Yakov Zdanov:*
>>> > IGNITE-4799 <https://issues.apache.org/jira/browse/IGNITE-4799> -
>>> Remove
>>> > TcpDiscoverySpi.heartbeatsFrequency parameter
>>> >
>>> >
>>> > *Denis*, we still have 5 issues that are *unassigned*. Are they
>>> supposed to
>>> > be getting into release?
>>> >
>>> > IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488> -
>>> Prohibit
>>> > null as name in all the components (cache name first of all).
>>> > IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596> -
>>> Hadoop
>>> > edition can't be compiled against spark 2.0.0
>>> > IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794> -
>>> > Reconsider
>>> > CachePeekMode.ONHEAP
>>> > IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202> -
>>> Local
>>> > server query result doesn't include versions in entries
>>> > IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398> -
>>> .NET:
>>> > Change default mapper behavior
>>> >
>>> >
>>> > D.
>>> >
>>> > On Wed, Apr 5, 2017 at 6:07 PM, Denis Magda <[hidden email]> wrote:
>>> >
>>> > Dmitriy,
>>> >
>>> > You can find all the required tickets with contributors assigned here:
>>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
>>> > ApacheIgnite2.0-Requiredtickets <https://cwiki.apache.org/
>>> > confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-
>>> > Requiredtickets>
>>> >
>>> > In short, Alex G., Sergi, Vovan, Taras, Yakov, Sam, etc. (almost all
>>> the
>>> > community) please share your readiness with the rest of the community.
>>> >
>>> > —
>>> > Denis
>>> >
>>> > On Apr 5, 2017, at 9:03 PM, Dmitriy Setrakyan <[hidden email]>
>>> >
>>> > wrote:
>>> >
>>> >
>>> > Denis,
>>> >
>>> > I think it will be worth while to list all the tickets by status
>>> together
>>> > with a name of the engineer assigned to it. This way most folks
>>> involved
>>> > would provide a response sooner.
>>> >
>>> > What do you think?
>>> >
>>> > D.
>>> >
>>> > On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda <[hidden email]> wrote:
>>> >
>>> > Igniters,
>>> >
>>> > What’s the overall status of 2.0 release? I see that many tickets
>>> >
>>> > related
>>> >
>>> > to the page memory [1] are still in the open state and, looks like,
>>> this
>>> > new memory architecture has not been fully merged yet. In addition, a
>>> >
>>> > new
>>> >
>>> > version of H2 has to be released prior to 2.0.
>>> >
>>> > All this threatens the release schedule we agreed on. According to the
>>> > plan the next week is a week of code freeze:
>>> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
>>> > ApacheIgnite2.0-Releasephases <https://cwiki.apache.org/
>>> > confluence/display/IGNITE/Apache+Ignite+2.0#
>>> >
>>> > ApacheIgnite2.0-Releasephases>
>>> >
>>> >
>>> > [1] https://issues.apache.org/jira/browse/IGNITE-3477 <
>>> > https://issues.apache.org/jira/browse/IGNITE-3477>
>>> >
>>> > —
>>> > Denis
>>> >
>>> > On Mar 31, 2017, at 4:02 AM, Vladimir Ozerov <[hidden email]>
>>> >
>>> > wrote:
>>> >
>>> >
>>> > Another big merge - now almost all our setters on public configuration
>>> > return "this" instance to allow for convenient chaining [1]. Big
>>> > thanks to *Andrew
>>> > Mashenkov* for making this happen.
>>> > Ideally I would also try to replace "set(Collection<Something>)" with "
>>> > set(Something...)". This should make configuration even more easier.
>>> >
>>> > [1] https://issues.apache.org/jira/browse/IGNITE-4564
>>> >
>>> > On Fri, Mar 31, 2017 at 2:18 AM, Denis Magda <[hidden email]>
>>> >
>>> > wrote:
>>> >
>>> >
>>> > Vovan,
>>> >
>>> > I expect to finalize and merge Spring Data Integration by the code
>>> >
>>> > freeze
>>> >
>>> > time (April 14th):
>>> > IGNITE-1192Provide integration with Spring Data <
>>> > https://issues.apache.org/jira/browse/IGNITE-1192>
>>> >
>>> > —
>>> > Denis
>>> >
>>> > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov <[hidden email]>
>>> >
>>> > wrote:
>>> >
>>> >
>>> > Igniters,
>>> >
>>> > We are getting closer to proposed code freeze date. Could you please
>>> >
>>> > go
>>> >
>>> > through the list of required [1] tickets and provide brief update on
>>> >
>>> > where
>>> >
>>> > we are?
>>> >
>>> > As per myself, I am curerntly working on CREATE/DROP index feature
>>> > stabilization and expect it to be ready for review on the next week.
>>> >
>>> > Vladimir.
>>> >
>>> > [1] https://cwiki.apache.org/confluence/display/IGNITE/
>>> >
>>> > Apache+Ignite+2.0
>>> >
>>> >
>>> > On Tue, Mar 28, 2017 at 9:11 PM, nivanov <[hidden email]>
>>> >
>>> > wrote:
>>> >
>>> >
>>> > I think we can make it on time to add IgniteML (a.k.a. distributed
>>> >
>>> > math) to
>>> >
>>> > 2.0 release pipeline.
>>> >
>>> >
>>> >
>>> > --
>>> > View this message in context: http://apache-ignite-
>>> > developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-
>>> > tp15690p15857.html
>>> > Sent from the Apache Ignite Developers mailing list archive at
>>> >
>>> > Nabble.com.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>>
>>
>>
>

Pavel Tupitsyn

Re: Apache Ignite 2.0 Release

I have went through my issues and moved most of them to 2.1.

However, the following looks very important: https://issues.apache.org/
jira/browse/IGNITE-4354 DML: BinaryObjectBuilder does not sort fields in
some cases

Alexander Paschenko, I think you have worked on field sorting, can you have
a look?

On Thu, Apr 6, 2017 at 3:23 PM, Vladimir Ozerov <[hidden email]>
wrote:

> I am almost done with DDL. It will be available for review in the nearest
> time.
>
> On Thu, Apr 6, 2017 at 1:38 PM, Vladimir Ozerov <[hidden email]>
> wrote:
>
> > Convenient filter to view your tickets (you must be logged in to JIRA):
> > <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.0%20AND%20resolution%20%3D%20Unresolved%20AND%20(
> > assignee%20%3D%20currentUser()%20OR%20reporter%20%3D%
> > 20currentUser())%20ORDER%20BY%20created%20ASC
> >
> > On Thu, Apr 6, 2017 at 1:34 PM, Vladimir Ozerov <[hidden email]>
> > wrote:
> >
> >> Folks,
> >>
> >> I would also encourage you to review all 2,0 tickets that are either
> >> assigned to you or submitted by you and move them to the next version
> (2.1)
> >> if you cannot complete them in the nearest time. Currently we have 554
> >> opened tickets for 2.0. Let's make sure that we have about several
> dozens
> >> in the nearest time.
> >>
> >> Thank you.
> >>
> >> On Thu, Apr 6, 2017 at 12:58 PM, Вадим Опольский <[hidden email]>
> >> wrote:
> >>
> >>> Hello community!
> >>>
> >>> Denis, issue IGNITE-1794
> >>> <https://issues.apache.org/jira/browse/IGNITE-1794> - Hibernate 5
> >>> Support
> >>> has been ready for review from 24 March.
> >>>
> >>> The tests in Team City executed successfully.
> >>>
> >>> Vadim Opolski
> >>>
> >>> 2017-04-06 5:04 GMT+03:00 Denis Magda <[hidden email]>:
> >>>
> >>> > *Denis Magda:*
> >>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
> >>> Provide
> >>> > integration with Spring Data
> >>> >
> >>> >
> >>> > Will be finished and merged by the code freeze date. I’m on a
> business
> >>> > trip now and don’t have extra time to complete the feature.
> >>> >
> >>> > Plus, following your template these are additional tickets:
> >>> >
> >>> > *Alexey Kuznetsov*
> >>> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> >>> Discontinue
> >>> > the schema-import utility
> >>> >
> >>> > *Sergey Chugunov*
> >>> > IGNITE-4536 <https://issues.apache.org/jira/browse/IGNITE-4536> -
> >>> Update
> >>> > metrics for new offheap storage
> >>> >
> >>> > *Nikita Ivanov*
> >>> > IGNITE-4572 <https://issues.apache.org/jira/browse/IGNITE-4572> -
> >>> Machine
> >>> > Learning: Develop distributed algebra support for dense and sparse
> data
> >>> > sets.
> >>> >
> >>> > *Roman Shtykh*
> >>> > IGNITE-4539 <https://issues.apache.org/jira/browse/IGNITE-4539> -
> >>> > RocketMQ Data Streamer
> >>> >
> >>> > *Vadim Opolski*
> >>> > IGNITE-1794 <https://issues.apache.org/jira/browse/IGNITE-1794> -
> >>> > Hibernate 5 Support
> >>> >
> >>> > —
> >>> > Denis
> >>> >
> >>> > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <[hidden email]
> >
> >>> > wrote:
> >>> >
> >>> > Guys,
> >>> >
> >>> > Please provide a status underneath every ticket listed below, so we
> >>> can get
> >>> > a full picture in one email thread:
> >>> >
> >>> > *Alexey Goncharuk:*
> >>> > IGNITE-3477 <https://issues.apache.org/jira/browse/IGNITE-3477> -
> >>> Rework
> >>> > offheap storage
> >>> > IGNITE-4337 <https://issues.apache.org/jira/browse/IGNITE-4337> -
> >>> > Introduce
> >>> > persistence interface to allow build reliable persistence plugins
> >>> >
> >>> > *Alexander Menshikov:*
> >>> > IGNITE-4699 <https://issues.apache.org/jira/browse/IGNITE-4699> -
> >>> > Introduce
> >>> > custom configurable executors.
> >>> >
> >>> > *Denis Magda:*
> >>> > IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> -
> >>> Provide
> >>> > integration with Spring Data
> >>> >
> >>> > *Dmitriy Karachentsev:*
> >>> > IGNITE-4477 <https://issues.apache.org/jira/browse/IGNITE-4477> -
> Fix
> >>> > IgniteFuture.listen() and IgniteFuture.chain() semantics
> >>> >
> >>> > *Ilya Lantukh:*
> >>> > IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535>
> >>> > <https://issues.apache.org/jira/browse/IGNITE-4535>- Add option to
> >>> store
> >>> > deserialized values on-heap
> >>> >
> >>> > *Ivan Rakov:*
> >>> > IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> -
> >>> > Implement
> >>> > offheap eviction policies based on page memory
> >>> >
> >>> > *Sergey Kalashnikov:*
> >>> > IGNITE-3595 <https://issues.apache.org/jira/browse/IGNITE-3595> -
> >>> Improve
> >>> > Enum fields handling in SQL.
> >>> >
> >>> > *Sergi Vladykin:*
> >>> > IGNITE-3869 <https://issues.apache.org/jira/browse/IGNITE-3869> -
> >>> Reduce
> >>> > number of temporary objects produced by H2
> >>> >
> >>> > *Taras Ledkov:*
> >>> > IGNITE-3469 <https://issues.apache.org/jira/browse/IGNITE-3469> -
> Get
> >>> rid
> >>> > of deprecated APIs and entities
> >>> >
> >>> > *Vladimir Ozerov:*
> >>> > IGNITE-4565 <https://issues.apache.org/jira/browse/IGNITE-4565> -
> >>> Support
> >>> > CREATE INDEX DDL statements
> >>> >
> >>> > *Yakov Zdanov:*
> >>> > IGNITE-4799 <https://issues.apache.org/jira/browse/IGNITE-4799> -
> >>> Remove
> >>> > TcpDiscoverySpi.heartbeatsFrequency parameter
> >>> >
> >>> >
> >>> > *Denis*, we still have 5 issues that are *unassigned*. Are they
> >>> supposed to
> >>> > be getting into release?
> >>> >
> >>> > IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488> -
> >>> Prohibit
> >>> > null as name in all the components (cache name first of all).
> >>> > IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596> -
> >>> Hadoop
> >>> > edition can't be compiled against spark 2.0.0
> >>> > IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794> -
> >>> > Reconsider
> >>> > CachePeekMode.ONHEAP
> >>> > IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202> -
> >>> Local
> >>> > server query result doesn't include versions in entries
> >>> > IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398> -
> >>> .NET:
> >>> > Change default mapper behavior
> >>> >
> >>> >
> >>> > D.
> >>> >
> >>> > On Wed, Apr 5, 2017 at 6:07 PM, Denis Magda <[hidden email]>
> wrote:
> >>> >
> >>> > Dmitriy,
> >>> >
> >>> > You can find all the required tickets with contributors assigned
> here:
> >>> > https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.0#
> >>> > ApacheIgnite2.0-Requiredtickets <https://cwiki.apache.org/
> >>> > confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-
> >>> > Requiredtickets>
> >>> >
> >>> > In short, Alex G., Sergi, Vovan, Taras, Yakov, Sam, etc. (almost all
> >>> the
> >>> > community) please share your readiness with the rest of the
> community.
> >>> >
> >>> > —
> >>> > Denis
> >>> >
> >>> > On Apr 5, 2017, at 9:03 PM, Dmitriy Setrakyan <[hidden email]
> >
> >>> >
> >>> > wrote:
> >>> >
> >>> >
> >>> > Denis,
> >>> >
> >>> > I think it will be worth while to list all the tickets by status
> >>> together
> >>> > with a name of the engineer assigned to it. This way most folks
> >>> involved
> >>> > would provide a response sooner.
> >>> >
> >>> > What do you think?
> >>> >
> >>> > D.
> >>> >
> >>> > On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda <[hidden email]>
> wrote:
> >>> >
> >>> > Igniters,
> >>> >
> >>> > What’s the overall status of 2.0 release? I see that many tickets
> >>> >
> >>> > related
> >>> >
> >>> > to the page memory [1] are still in the open state and, looks like,
> >>> this
> >>> > new memory architecture has not been fully merged yet. In addition, a
> >>> >
> >>> > new
> >>> >
> >>> > version of H2 has to be released prior to 2.0.
> >>> >
> >>> > All this threatens the release schedule we agreed on. According to
> the
> >>> > plan the next week is a week of code freeze:
> >>> > https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.0#
> >>> > ApacheIgnite2.0-Releasephases <https://cwiki.apache.org/
> >>> > confluence/display/IGNITE/Apache+Ignite+2.0#
> >>> >
> >>> > ApacheIgnite2.0-Releasephases>
> >>> >
> >>> >
> >>> > [1] https://issues.apache.org/jira/browse/IGNITE-3477 <
> >>> > https://issues.apache.org/jira/browse/IGNITE-3477>
> >>> >
> >>> > —
> >>> > Denis
> >>> >
> >>> > On Mar 31, 2017, at 4:02 AM, Vladimir Ozerov <[hidden email]>
> >>> >
> >>> > wrote:
> >>> >
> >>> >
> >>> > Another big merge - now almost all our setters on public
> configuration
> >>> > return "this" instance to allow for convenient chaining [1]. Big
> >>> > thanks to *Andrew
> >>> > Mashenkov* for making this happen.
> >>> > Ideally I would also try to replace "set(Collection<Something>)"
> with "
> >>> > set(Something...)". This should make configuration even more easier.
> >>> >
> >>> > [1] https://issues.apache.org/jira/browse/IGNITE-4564
> >>> >
> >>> > On Fri, Mar 31, 2017 at 2:18 AM, Denis Magda <[hidden email]>
> >>> >
> >>> > wrote:
> >>> >
> >>> >
> >>> > Vovan,
> >>> >
> >>> > I expect to finalize and merge Spring Data Integration by the code
> >>> >
> >>> > freeze
> >>> >
> >>> > time (April 14th):
> >>> > IGNITE-1192Provide integration with Spring Data <
> >>> > https://issues.apache.org/jira/browse/IGNITE-1192>
> >>> >
> >>> > —
> >>> > Denis
> >>> >
> >>> > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov <[hidden email]>
> >>> >
> >>> > wrote:
> >>> >
> >>> >
> >>> > Igniters,
> >>> >
> >>> > We are getting closer to proposed code freeze date. Could you please
> >>> >
> >>> > go
> >>> >
> >>> > through the list of required [1] tickets and provide brief update on
> >>> >
> >>> > where
> >>> >
> >>> > we are?
> >>> >
> >>> > As per myself, I am curerntly working on CREATE/DROP index feature
> >>> > stabilization and expect it to be ready for review on the next week.
> >>> >
> >>> > Vladimir.
> >>> >
> >>> > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> >>> >
> >>> > Apache+Ignite+2.0
> >>> >
> >>> >
> >>> > On Tue, Mar 28, 2017 at 9:11 PM, nivanov <[hidden email]>
> >>> >
> >>> > wrote:
> >>> >
> >>> >
> >>> > I think we can make it on time to add IgniteML (a.k.a. distributed
> >>> >
> >>> > math) to
> >>> >
> >>> > 2.0 release pipeline.
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > View this message in context: http://apache-ignite-
> >>> > developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-
> >>> > tp15690p15857.html
> >>> > Sent from the Apache Ignite Developers mailing list archive at
> >>> >
> >>> > Nabble.com.
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>> >
> >>>
> >>
> >>
> >
>

Alexey Kuznetsov

Re: Apache Ignite 2.0 Release

I've prepared

IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
Discontinue the schema-import utility

Anton, could you review my changes related to Ignite *build*?
See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163

--
Alexey Kuznetsov

Alexey Goncharuk

Re: Apache Ignite 2.0 Release

Folks,

The status of ignite-3477 is as follows: we've fixed almost all tests and
currently waiting for ignite-4535 and ignite-4534 to be merged, which will
happen once TC for those branches is completed. This should happen over the
weekend.

2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]>:

> I've prepared
>
> IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> Discontinue the schema-import utility
>
> Anton, could you review my changes related to Ignite *build*?
> See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
>
>
> --
> Alexey Kuznetsov
>

dsetrakyan

Re: Apache Ignite 2.0 Release

Alexey g,

Thanks for the update.

If IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> and
IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535> are close
to being merged to master, how come they are not in PATCH AVAILABLE status?

Also, what is the status of IGNITE-4337
<https://issues.apache.org/jira/browse/IGNITE-4337> - Introduce persistence
interface to allow build reliable persistence plugins?

D.

On Fri, Apr 7, 2017 at 9:36 AM, Alexey Goncharuk <[hidden email]
> wrote:

> Folks,
>
> The status of ignite-3477 is as follows: we've fixed almost all tests and
> currently waiting for ignite-4535 and ignite-4534 to be merged, which will
> happen once TC for those branches is completed. This should happen over the
> weekend.
>
> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
>
> > I've prepared
> >
> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> > Discontinue the schema-import utility
> >
> > Anton, could you review my changes related to Ignite *build*?
> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> >
> >
> > --
> > Alexey Kuznetsov
> >
>

Sergi

Re: Apache Ignite 2.0 Release

In reply to this post by Alexey Goncharuk

A bunch of SQL related tickets is delayed until H2 release on the next week.

Sergi

2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <[hidden email]>:

al.psc

Re: Apache Ignite 2.0 Release

I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
https://github.com/apache/ignite/pull/1759.
Pavel, thank you very much for bringing that to my attention.

- Alex

2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]>:

> A bunch of SQL related tickets is delayed until H2 release on the next week.
>
> Sergi
>
> 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <[hidden email]>:
>
>> Folks,
>>
>> The status of ignite-3477 is as follows: we've fixed almost all tests and
>> currently waiting for ignite-4535 and ignite-4534 to be merged, which will
>> happen once TC for those branches is completed. This should happen over the
>> weekend.
>>
>> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
>>
>> > I've prepared
>> >
>> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
>> > Discontinue the schema-import utility
>> >
>> > Anton, could you review my changes related to Ignite *build*?
>> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
>> >
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>

Valentin Kulichenko

Re: Apache Ignite 2.0 Release

Guys,

There is no branch for 2.0 right now, correct? If I want to add something
there, do I just merge to master?

-Val

On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
[hidden email]> wrote:

> I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
> https://github.com/apache/ignite/pull/1759.
> Pavel, thank you very much for bringing that to my attention.
>
> - Alex
>
> 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]>:
> > A bunch of SQL related tickets is delayed until H2 release on the next
> week.
> >
> > Sergi
> >
> > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <[hidden email]
> >:
> >
> >> Folks,
> >>
> >> The status of ignite-3477 is as follows: we've fixed almost all tests
> and
> >> currently waiting for ignite-4535 and ignite-4534 to be merged, which
> will
> >> happen once TC for those branches is completed. This should happen over
> the
> >> weekend.
> >>
> >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
> >>
> >> > I've prepared
> >> >
> >> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> >> > Discontinue the schema-import utility
> >> >
> >> > Anton, could you review my changes related to Ignite *build*?
> >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> >> >
> >> >
> >> > --
> >> > Alexey Kuznetsov
> >> >
> >>
>

Denis Magda

Re: Apache Ignite 2.0 Release

Val, yes, as far as I know we still need to merge to the master. The branch
should be ready later the next week.

Denis

On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
[hidden email]> wrote:

> Guys,
>
> There is no branch for 2.0 right now, correct? If I want to add something
> there, do I just merge to master?
>
> -Val
>
> On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> [hidden email]> wrote:
>
> > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is
> > https://github.com/apache/ignite/pull/1759.
> > Pavel, thank you very much for bringing that to my attention.
> >
> > - Alex
> >
> > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]>:
> > > A bunch of SQL related tickets is delayed until H2 release on the next
> > week.
> > >
> > > Sergi
> > >
> > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> [hidden email]
> > >:
> > >
> > >> Folks,
> > >>
> > >> The status of ignite-3477 is as follows: we've fixed almost all tests
> > and
> > >> currently waiting for ignite-4535 and ignite-4534 to be merged, which
> > will
> > >> happen once TC for those branches is completed. This should happen
> over
> > the
> > >> weekend.
> > >>
> > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]>:
> > >>
> > >> > I've prepared
> > >> >
> > >> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> -
> > >> > Discontinue the schema-import utility
> > >> >
> > >> > Anton, could you review my changes related to Ignite *build*?
> > >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> > >> >
> > >> >
> > >> > --
> > >> > Alexey Kuznetsov
> > >> >
> > >>
> >
>

dmagda

Re: Apache Ignite 2.0 Release

Spring Data integration caught up the train and will be released in 2.0:
https://issues.apache.org/jira/browse/IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192>

—
Denis

> On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
>
> Val, yes, as far as I know we still need to merge to the master. The branch should be ready later the next week.
>
> Denis
>
> On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <[hidden email] <mailto:[hidden email]>> wrote:
> Guys,
>
> There is no branch for 2.0 right now, correct? If I want to add something
> there, do I just merge to master?
>
> -Val
>
> On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> [hidden email] <mailto:[hidden email]>> wrote:
>
> > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > https://github.com/apache/ignite/pull/1759 <https://github.com/apache/ignite/pull/1759>.
> > Pavel, thank you very much for bringing that to my attention.
> >
> > - Alex
> >
> > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email] <mailto:[hidden email]>>:
> > > A bunch of SQL related tickets is delayed until H2 release on the next
> > week.
> > >
> > > Sergi
> > >
> > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <[hidden email] <mailto:[hidden email]>
> > >:
> > >
> > >> Folks,
> > >>
> > >> The status of ignite-3477 is as follows: we've fixed almost all tests
> > and
> > >> currently waiting for ignite-4535 and ignite-4534 to be merged, which
> > will
> > >> happen once TC for those branches is completed. This should happen over
> > the
> > >> weekend.
> > >>
> > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email] <mailto:[hidden email]>>:
> > >>
> > >> > I've prepared
> > >> >
> > >> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > >> > Discontinue the schema-import utility
> > >> >
> > >> > Anton, could you review my changes related to Ignite *build*?
> > >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163 <http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > >> >
> > >> >
> > >> > --
> > >> > Alexey Kuznetsov
> > >> >
> > >>
> >
>

dsetrakyan

Re: Apache Ignite 2.0 Release

Awesome! Great addition to the project.

On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]> wrote:

> Spring Data integration caught up the train and will be released in 2.0:
> https://issues.apache.org/jira/browse/IGNITE-1192 <
> https://issues.apache.org/jira/browse/IGNITE-1192>
>
> —
> Denis
>
> > On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
> >
> > Val, yes, as far as I know we still need to merge to the master. The
> branch should be ready later the next week.
> >
> > Denis
> >
> > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> [hidden email] <mailto:[hidden email]>>
> wrote:
> > Guys,
> >
> > There is no branch for 2.0 right now, correct? If I want to add something
> > there, do I just merge to master?
> >
> > -Val
> >
> > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > [hidden email] <mailto:[hidden email]>>
> wrote:
> >
> > > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > > https://github.com/apache/ignite/pull/1759 <https://github.com/apache/
> ignite/pull/1759>.
> > > Pavel, thank you very much for bringing that to my attention.
> > >
> > > - Alex
> > >
> > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]
> <mailto:[hidden email]>>:
> > > > A bunch of SQL related tickets is delayed until H2 release on the
> next
> > > week.
> > > >
> > > > Sergi
> > > >
> > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> [hidden email] <mailto:[hidden email]>
> > > >:
> > > >
> > > >> Folks,
> > > >>
> > > >> The status of ignite-3477 is as follows: we've fixed almost all
> tests
> > > and
> > > >> currently waiting for ignite-4535 and ignite-4534 to be merged,
> which
> > > will
> > > >> happen once TC for those branches is completed. This should happen
> over
> > > the
> > > >> weekend.
> > > >>
> > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <[hidden email]
> <mailto:[hidden email]>>:
> > > >>
> > > >> > I've prepared
> > > >> >
> > > >> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349 <
> https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > > >> > Discontinue the schema-import utility
> > > >> >
> > > >> > Anton, could you review my changes related to Ignite *build*?
> > > >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163 <
> http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > > >> >
> > > >> >
> > > >> > --
> > > >> > Alexey Kuznetsov
> > > >> >
> > > >>
> > >
> >
>
>

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

Folks,

I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue
2.0 finalization in this branch.

On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Awesome! Great addition to the project.
>
> On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]> wrote:
>
> > Spring Data integration caught up the train and will be released in 2.0:
> > https://issues.apache.org/jira/browse/IGNITE-1192 <
> > https://issues.apache.org/jira/browse/IGNITE-1192>
> >
> > —
> > Denis
> >
> > > On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
> > >
> > > Val, yes, as far as I know we still need to merge to the master. The
> > branch should be ready later the next week.
> > >
> > > Denis
> > >
> > > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> > [hidden email] <mailto:[hidden email]>>
> > wrote:
> > > Guys,
> > >
> > > There is no branch for 2.0 right now, correct? If I want to add
> something
> > > there, do I just merge to master?
> > >
> > > -Val
> > >
> > > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > > [hidden email] <mailto:alexander.a.paschenko@
> gmail.com>>
> > wrote:
> > >
> > > > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> > https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > > > https://github.com/apache/ignite/pull/1759 <
> https://github.com/apache/
> > ignite/pull/1759>.
> > > > Pavel, thank you very much for bringing that to my attention.
> > > >
> > > > - Alex
> > > >
> > > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]
> > <mailto:[hidden email]>>:
> > > > > A bunch of SQL related tickets is delayed until H2 release on the
> > next
> > > > week.
> > > > >
> > > > > Sergi
> > > > >
> > > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> > [hidden email] <mailto:[hidden email]>
> > > > >:
> > > > >
> > > > >> Folks,
> > > > >>
> > > > >> The status of ignite-3477 is as follows: we've fixed almost all
> > tests
> > > > and
> > > > >> currently waiting for ignite-4535 and ignite-4534 to be merged,
> > which
> > > > will
> > > > >> happen once TC for those branches is completed. This should happen
> > over
> > > > the
> > > > >> weekend.
> > > > >>
> > > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> [hidden email]
> > <mailto:[hidden email]>>:
> > > > >>
> > > > >> > I've prepared
> > > > >> >
> > > > >> > IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349
> <
> > https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > > > >> > Discontinue the schema-import utility
> > > > >> >
> > > > >> > Anton, could you review my changes related to Ignite *build*?
> > > > >> > See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> <
> > http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> > Alexey Kuznetsov
> > > > >> >
> > > > >>
> > > >
> > >
> >
> >
>

Alexey Goncharuk

Re: Apache Ignite 2.0 Release

Hi Roman,

I tried to run tests for RocketMQ streamer, but they failed for me (I've
added a comment in the ticket). Can you please take a look?

2017-04-18 15:13 GMT+03:00 Vladimir Ozerov <[hidden email]>:

> Folks,
>
> I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue
> 2.0 finalization in this branch.
>
> On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
> > Awesome! Great addition to the project.
> >
> > On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]> wrote:
> >
> > > Spring Data integration caught up the train and will be released in
> 2.0:
> > > https://issues.apache.org/jira/browse/IGNITE-1192 <
> > > https://issues.apache.org/jira/browse/IGNITE-1192>
> > >
> > > —
> > > Denis
> > >
> > > > On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
> > > >
> > > > Val, yes, as far as I know we still need to merge to the master. The
> > > branch should be ready later the next week.
> > > >
> > > > Denis
> > > >
> > > > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> > > [hidden email] <mailto:[hidden email]>>
> > > wrote:
> > > > Guys,
> > > >
> > > > There is no branch for 2.0 right now, correct? If I want to add
> > something
> > > > there, do I just merge to master?
> > > >
> > > > -Val
> > > >
> > > > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > > > [hidden email] <mailto:alexander.a.paschenko@
> > gmail.com>>
> > > wrote:
> > > >
> > > > > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> > > https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > > > > https://github.com/apache/ignite/pull/1759 <
> > https://github.com/apache/
> > > ignite/pull/1759>.
> > > > > Pavel, thank you very much for bringing that to my attention.
> > > > >
> > > > > - Alex
> > > > >
> > > > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <
> [hidden email]
> > > <mailto:[hidden email]>>:
> > > > > > A bunch of SQL related tickets is delayed until H2 release on the
> > > next
> > > > > week.
> > > > > >
> > > > > > Sergi
> > > > > >
> > > > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> > > [hidden email] <mailto:[hidden email]>
> > > > > >:
> > > > > >
> > > > > >> Folks,
> > > > > >>
> > > > > >> The status of ignite-3477 is as follows: we've fixed almost all
> > > tests
> > > > > and
> > > > > >> currently waiting for ignite-4535 and ignite-4534 to be merged,
> > > which
> > > > > will
> > > > > >> happen once TC for those branches is completed. This should
> happen
> > > over
> > > > > the
> > > > > >> weekend.
> > > > > >>
> > > > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> > [hidden email]
> > > <mailto:[hidden email]>>:
> > > > > >>
> > > > > >> > I've prepared
> > > > > >> >
> > > > > >> > IGNITE-4349 <https://issues.apache.org/
> jira/browse/IGNITE-4349
> > <
> > > https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > > > > >> > Discontinue the schema-import utility
> > > > > >> >
> > > > > >> > Anton, could you review my changes related to Ignite *build*?
> > > > > >> > See: http://reviews.ignite.apache.
> org/ignite/review/IGNT-CR-163
> > <
> > > http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> > Alexey Kuznetsov
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> > >
> >
>

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

CREATE/DROP INDEX feature [1] has been merged to release branch.

[1] https://issues.apache.org/jira/browse/IGNITE-4565

On Tue, Apr 18, 2017 at 4:10 PM, Alexey Goncharuk <
[hidden email]> wrote:

> Hi Roman,
>
> I tried to run tests for RocketMQ streamer, but they failed for me (I've
> added a comment in the ticket). Can you please take a look?
>
> 2017-04-18 15:13 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > Folks,
> >
> > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's
> continue
> > 2.0 finalization in this branch.
> >
> > On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> > > Awesome! Great addition to the project.
> > >
> > > On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > > > Spring Data integration caught up the train and will be released in
> > 2.0:
> > > > https://issues.apache.org/jira/browse/IGNITE-1192 <
> > > > https://issues.apache.org/jira/browse/IGNITE-1192>
> > > >
> > > > —
> > > > Denis
> > > >
> > > > > On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]>
> wrote:
> > > > >
> > > > > Val, yes, as far as I know we still need to merge to the master.
> The
> > > > branch should be ready later the next week.
> > > > >
> > > > > Denis
> > > > >
> > > > > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> > > > [hidden email] <mailto:[hidden email]
> >>
> > > > wrote:
> > > > > Guys,
> > > > >
> > > > > There is no branch for 2.0 right now, correct? If I want to add
> > > something
> > > > > there, do I just merge to master?
> > > > >
> > > > > -Val
> > > > >
> > > > > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > > > > [hidden email] <mailto:alexander.a.paschenko@
> > > gmail.com>>
> > > > wrote:
> > > > >
> > > > > > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> > > > https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > > > > > https://github.com/apache/ignite/pull/1759 <
> > > https://github.com/apache/
> > > > ignite/pull/1759>.
> > > > > > Pavel, thank you very much for bringing that to my attention.
> > > > > >
> > > > > > - Alex
> > > > > >
> > > > > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <
> > [hidden email]
> > > > <mailto:[hidden email]>>:
> > > > > > > A bunch of SQL related tickets is delayed until H2 release on
> the
> > > > next
> > > > > > week.
> > > > > > >
> > > > > > > Sergi
> > > > > > >
> > > > > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> > > > [hidden email] <mailto:[hidden email]>
> > > > > > >:
> > > > > > >
> > > > > > >> Folks,
> > > > > > >>
> > > > > > >> The status of ignite-3477 is as follows: we've fixed almost
> all
> > > > tests
> > > > > > and
> > > > > > >> currently waiting for ignite-4535 and ignite-4534 to be
> merged,
> > > > which
> > > > > > will
> > > > > > >> happen once TC for those branches is completed. This should
> > happen
> > > > over
> > > > > > the
> > > > > > >> weekend.
> > > > > > >>
> > > > > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> > > [hidden email]
> > > > <mailto:[hidden email]>>:
> > > > > > >>
> > > > > > >> > I've prepared
> > > > > > >> >
> > > > > > >> > IGNITE-4349 <https://issues.apache.org/
> > jira/browse/IGNITE-4349
> > > <
> > > > https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > > > > > >> > Discontinue the schema-import utility
> > > > > > >> >
> > > > > > >> > Anton, could you review my changes related to Ignite
> *build*?
> > > > > > >> > See: http://reviews.ignite.apache.
> > org/ignite/review/IGNT-CR-163
> > > <
> > > > http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> > Alexey Kuznetsov
> > > > > > >> >
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

dmagda

Re: Apache Ignite 2.0 Release

In reply to this post by Vladimir Ozerov

Vovan,

Do I need to commit a 2.0 change to ignite-2.0 first and then merge it back to the master? What’s the process?

—
Denis

> On Apr 18, 2017, at 5:13 AM, Vladimir Ozerov <[hidden email]> wrote:
>
> Folks,
>
> I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue
> 2.0 finalization in this branch.
>
> On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <[hidden email]>
> wrote:
>
>> Awesome! Great addition to the project.
>>
>> On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]> wrote:
>>
>>> Spring Data integration caught up the train and will be released in 2.0:
>>> https://issues.apache.org/jira/browse/IGNITE-1192 <
>>> https://issues.apache.org/jira/browse/IGNITE-1192>
>>>
>>> —
>>> Denis
>>>
>>>> On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
>>>>
>>>> Val, yes, as far as I know we still need to merge to the master. The
>>> branch should be ready later the next week.
>>>>
>>>> Denis
>>>>
>>>> On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
>>> [hidden email] <mailto:[hidden email]>>
>>> wrote:
>>>> Guys,
>>>>
>>>> There is no branch for 2.0 right now, correct? If I want to add
>> something
>>>> there, do I just merge to master?
>>>>
>>>> -Val
>>>>
>>>> On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
>>>> [hidden email] <mailto:alexander.a.paschenko@
>> gmail.com>>
>>> wrote:
>>>>
>>>>> I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
>>> https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
>>>>> https://github.com/apache/ignite/pull/1759 <
>> https://github.com/apache/
>>> ignite/pull/1759>.
>>>>> Pavel, thank you very much for bringing that to my attention.
>>>>>
>>>>> - Alex
>>>>>
>>>>> 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]
>>> <mailto:[hidden email]>>:
>>>>>> A bunch of SQL related tickets is delayed until H2 release on the
>>> next
>>>>> week.
>>>>>>
>>>>>> Sergi
>>>>>>
>>>>>> 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
>>> [hidden email] <mailto:[hidden email]>
>>>>>> :
>>>>>>
>>>>>>> Folks,
>>>>>>>
>>>>>>> The status of ignite-3477 is as follows: we've fixed almost all
>>> tests
>>>>> and
>>>>>>> currently waiting for ignite-4535 and ignite-4534 to be merged,
>>> which
>>>>> will
>>>>>>> happen once TC for those branches is completed. This should happen
>>> over
>>>>> the
>>>>>>> weekend.
>>>>>>>
>>>>>>> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
>> [hidden email]
>>> <mailto:[hidden email]>>:
>>>>>>>
>>>>>>>> I've prepared
>>>>>>>>
>>>>>>>> IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349
>> <
>>> https://issues.apache.org/jira/browse/IGNITE-4349>> -
>>>>>>>> Discontinue the schema-import utility
>>>>>>>>
>>>>>>>> Anton, could you review my changes related to Ignite *build*?
>>>>>>>> See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
>> <
>>> http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Alexey Kuznetsov
>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>
>>>
>>

Vladimir Ozerov

Re: Apache Ignite 2.0 Release

Denis,

As usual: merge to release branch at the very least. You can merge
ignite-2.0 -> master immediately then if you want, but it is not necessary.
ignite-2.0 will be merged to master eventually anyway.

On Tue, Apr 18, 2017 at 6:00 PM, Denis Magda <[hidden email]> wrote:

> Vovan,
>
> Do I need to commit a 2.0 change to ignite-2.0 first and then merge it
> back to the master? What’s the process?
>
> —
> Denis
>
> > On Apr 18, 2017, at 5:13 AM, Vladimir Ozerov <[hidden email]>
> wrote:
> >
> > Folks,
> >
> > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's
> continue
> > 2.0 finalization in this branch.
> >
> > On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> >> Awesome! Great addition to the project.
> >>
> >> On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]> wrote:
> >>
> >>> Spring Data integration caught up the train and will be released in
> 2.0:
> >>> https://issues.apache.org/jira/browse/IGNITE-1192 <
> >>> https://issues.apache.org/jira/browse/IGNITE-1192>
> >>>
> >>> —
> >>> Denis
> >>>
> >>>> On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]> wrote:
> >>>>
> >>>> Val, yes, as far as I know we still need to merge to the master. The
> >>> branch should be ready later the next week.
> >>>>
> >>>> Denis
> >>>>
> >>>> On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> >>> [hidden email] <mailto:[hidden email]>>
> >>> wrote:
> >>>> Guys,
> >>>>
> >>>> There is no branch for 2.0 right now, correct? If I want to add
> >> something
> >>>> there, do I just merge to master?
> >>>>
> >>>> -Val
> >>>>
> >>>> On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> >>>> [hidden email] <mailto:alexander.a.paschenko@
> >> gmail.com>>
> >>> wrote:
> >>>>
> >>>>> I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> >>> https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> >>>>> https://github.com/apache/ignite/pull/1759 <
> >> https://github.com/apache/
> >>> ignite/pull/1759>.
> >>>>> Pavel, thank you very much for bringing that to my attention.
> >>>>>
> >>>>> - Alex
> >>>>>
> >>>>> 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <[hidden email]
> >>> <mailto:[hidden email]>>:
> >>>>>> A bunch of SQL related tickets is delayed until H2 release on the
> >>> next
> >>>>> week.
> >>>>>>
> >>>>>> Sergi
> >>>>>>
> >>>>>> 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> >>> [hidden email] <mailto:[hidden email]>
> >>>>>> :
> >>>>>>
> >>>>>>> Folks,
> >>>>>>>
> >>>>>>> The status of ignite-3477 is as follows: we've fixed almost all
> >>> tests
> >>>>> and
> >>>>>>> currently waiting for ignite-4535 and ignite-4534 to be merged,
> >>> which
> >>>>> will
> >>>>>>> happen once TC for those branches is completed. This should happen
> >>> over
> >>>>> the
> >>>>>>> weekend.
> >>>>>>>
> >>>>>>> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> >> [hidden email]
> >>> <mailto:[hidden email]>>:
> >>>>>>>
> >>>>>>>> I've prepared
> >>>>>>>>
> >>>>>>>> IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349
> >> <
> >>> https://issues.apache.org/jira/browse/IGNITE-4349>> -
> >>>>>>>> Discontinue the schema-import utility
> >>>>>>>>
> >>>>>>>> Anton, could you review my changes related to Ignite *build*?
> >>>>>>>> See: http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163
> >> <
> >>> http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Alexey Kuznetsov
> >>>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>
>
>

Roman Shtykh

Re: Apache Ignite 2.0 Release

In reply to this post by Alexey Goncharuk

Hi Alexey,
Fixed now. Thanks for checking!
Roman

On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk <[hidden email]> wrote:

Hi Roman,

I tried to run tests for RocketMQ streamer, but they failed for me (I've
added a comment in the ticket). Can you please take a look?

2017-04-18 15:13 GMT+03:00 Vladimir Ozerov <[hidden email]>:

Alexey Goncharuk

Re: Apache Ignite 2.0 Release

Roman,

I see that you've changed the rocketmq version to 4.0.0-SNAPSHOT, but this
does not work because it requires a local copy of rocketmq. If I revert it
back to 4.0.0-incubating, then the test does not compile for me.

2017-04-19 11:55 GMT+03:00 Roman Shtykh <[hidden email]>:

> Hi Alexey,
> Fixed now. Thanks for checking!
> Roman
>
>
> On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk <
> [hidden email]> wrote:
>
>
> Hi Roman,
>
> I tried to run tests for RocketMQ streamer, but they failed for me (I've
> added a comment in the ticket). Can you please take a look?
>
> 2017-04-18 15:13 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
> > Folks,
> >
> > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's
> continue
> > 2.0 finalization in this branch.
> >
> > On Wed, Apr 12, 2017 at 7:58 AM, Dmitriy Setrakyan <
> [hidden email]>
> > wrote:
> >
> > > Awesome! Great addition to the project.
> > >
> > > On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda <[hidden email]>
> wrote:
> > >
> > > > Spring Data integration caught up the train and will be released in
> > 2.0:
> > > > https://issues.apache.org/jira/browse/IGNITE-1192 <
> > > > https://issues.apache.org/jira/browse/IGNITE-1192>
> > > >
> > > > —
> > > > Denis
> > > >
> > > > > On Apr 9, 2017, at 6:57 AM, Denis Magda <[hidden email]>
> wrote:
> > > > >
> > > > > Val, yes, as far as I know we still need to merge to the master.
> The
> > > > branch should be ready later the next week.
> > > > >
> > > > > Denis
> > > > >
> > > > > On Sat, Apr 8, 2017 at 6:14 PM, Valentin Kulichenko <
> > > > [hidden email] <mailto:[hidden email]
> >>
> > > > wrote:
> > > > > Guys,
> > > > >
> > > > > There is no branch for 2.0 right now, correct? If I want to add
> > > something
> > > > > there, do I just merge to master?
> > > > >
> > > > > -Val
> > > > >
> > > > > On Sat, Apr 8, 2017 at 10:18 AM, Alexander Paschenko <
> > > > > [hidden email] <mailto:alexander.a.paschenko@
> > > gmail.com>>
> > > > wrote:
> > > > >
> > > > > > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354 <
> > > > https://issues.apache.org/jira/browse/IGNITE-4354>, PR is
> > > > > > https://github.com/apache/ignite/pull/1759 <
> > > https://github.com/apache/
> > > > ignite/pull/1759>.
> > > > > > Pavel, thank you very much for bringing that to my attention.
> > > > > >
> > > > > > - Alex
> > > > > >
> > > > > > 2017-04-07 20:28 GMT+03:00 Sergi Vladykin <
> > [hidden email]
> > > > <mailto:[hidden email]>>:
> > > > > > > A bunch of SQL related tickets is delayed until H2 release on
> the
> > > > next
> > > > > > week.
> > > > > > >
> > > > > > > Sergi
> > > > > > >
> > > > > > > 2017-04-07 19:36 GMT+03:00 Alexey Goncharuk <
> > > > [hidden email] <mailto:[hidden email]>
> > > > > > >:
> > > > > > >
> > > > > > >> Folks,
> > > > > > >>
> > > > > > >> The status of ignite-3477 is as follows: we've fixed almost
> all
> > > > tests
> > > > > > and
> > > > > > >> currently waiting for ignite-4535 and ignite-4534 to be
> merged,
> > > > which
> > > > > > will
> > > > > > >> happen once TC for those branches is completed. This should
> > happen
> > > > over
> > > > > > the
> > > > > > >> weekend.
> > > > > > >>
> > > > > > >> 2017-04-06 19:12 GMT+03:00 Alexey Kuznetsov <
> > > [hidden email]
> > > > <mailto:[hidden email]>>:
> > > > > > >>
> > > > > > >> > I've prepared
> > > > > > >> >
> > > > > > >> > IGNITE-4349 <https://issues.apache.org/
> > jira/browse/IGNITE-4349
> > > <
> > > > https://issues.apache.org/jira/browse/IGNITE-4349>> -
> > > > > > >> > Discontinue the schema-import utility
> > > > > > >> >
> > > > > > >> > Anton, could you review my changes related to Ignite
> *build*?
> > > > > > >> > See: http://reviews.ignite.apache.
> > org/ignite/review/IGNT-CR-163
> > > <
> > > > http://reviews.ignite.apache.org/ignite/review/IGNT-CR-163>
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> > Alexey Kuznetsov
> > > > > > >> >
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
>
>
>

123