Re: Apache Ignite 2.0 Release

Igniters, Looks like all tickets for AI 2.0 are merged. I am going to start vote in the nearest time. On Wed, Apr 26, 2017 at 2:27 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Roman, > > Thanks for the contribution, I merged your changes to ignite-2.0 branch. > > 2017-04-26 7:12 G

Re: Apache Ignite 2.0 Release

Roman, Thanks for the contribution, I merged your changes to ignite-2.0 branch. 2017-04-26 7:12 GMT+03:00 Denis Magda : > Alex G., > > Would you complete the review of IGNITE-4539 and merge the changes? > > — > Denis > > > On Apr 25, 2017, at 6:33 PM, Roman Shtykh > wrote: > > > > I would also

Re: Apache Ignite 2.0 Release

Alex G., Would you complete the review of IGNITE-4539 and merge the changes? — Denis > On Apr 25, 2017, at 6:33 PM, Roman Shtykh wrote: > > I would also like to include IGNITE-4539. Its implementation is finished. > Roman > >On Wednesday, April 26, 2017 1:59 AM, Vladimir Ozerov > wrot

Re: Apache Ignite 2.0 Release

I would also like to include IGNITE-4539. Its implementation is finished. Roman On Wednesday, April 26, 2017 1:59 AM, Vladimir Ozerov wrote: Igniters, We are almost there. Outstanding issues which I hope we will be able to resolve quickly: 1) Hibernate 5 support [1] 2) Two SQL tickets

Re: Apache Ignite 2.0 Release

Igniters, We are almost there. Outstanding issues which I hope we will be able to resolve quickly: 1) Hibernate 5 support [1] 2) Two SQL tickets (2], [3] 3) Two page memory tickets [4], [5] 4) TcpDiscoverySpi.heartbeatsFrequency [6] 5) Prohibit "null" as cache name [7] Most of them are in "Patch

Re: Apache Ignite 2.0 Release

Guys, How close are we for the voting? What exactly are we waiting for to initiate it (H2 release, TC tests, CREATE INDEX)? — Denis > On Apr 19, 2017, at 4:03 PM, Denis Magda wrote: > > Roman, > > If we squeeze your contribution into 2.0 please add a documentation. You can > handle the docu

Re: Apache Ignite 2.0 Release

Roman, If we squeeze your contribution into 2.0 please add a documentation. You can handle the documentation separately as a subtask of this umbrella ticket: https://issues.apache.org/jira/browse/IGNITE-4960 — Denis > On Apr 19, 2017, at 7:03 AM, Roman Shtykh wrote: > > Alexey, > Sorry, I for

Re: Apache Ignite 2.0 Release

Alexey, Sorry, I forgot to update dependencies. Now it should be fine. Roman On Wednesday, April 19, 2017 9:56 PM, Alexey Goncharuk wrote: 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

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 : > Hi Alexey, > Fixed now. Thanks

Re: Apache Ignite 2.0 Release

Hi Alexey, Fixed now. Thanks for checking! Roman On Tuesday, April 18, 2017 10:17 PM, Alexey Goncharuk 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 Vlad

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 wrote: > Vovan, > > Do I need to commit a 2.0

Re: Apache Ignite 2.0 Release

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 wrote: > > Folks, > > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue > 2.0 finalization in

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 < alexey.goncha...@gmail.com> wrote: > Hi Roman, > > I tried to run tests for RocketMQ streamer, but they failed for me (I've >

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 : > Folks, > > I created branch for AI 2.0: ignite-2.0. Relevant PR #1819. Let's continue > 2.0 finalization i

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 wrote: > Awesome! Great addition to the project. > > On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda wrote: > > > Spring Data integ

Re: Apache Ignite 2.0 Release

Awesome! Great addition to the project. On Tue, Apr 11, 2017 at 8:27 PM, Denis Magda 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

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 — Denis > On Apr 9, 2017, at 6:57 AM, Denis Magda wrote: > > Val, yes, as far as I know we still need to merge to the m

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 < valentin.kuliche...@gmail.com> wrote: > Guys, > > There is no branch for 2.0 right now, correct? If I want to add something

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 < alexander.a.pasche...@gmail.com> wrote: > I've fixed https://issues.apache.org/jira/browse/IGNITE-4354, PR is > https://g

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 : > A bunch of SQL related tickets is delayed until H2 release on the next

Re: Apache Ignite 2.0 Release

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

Re: Apache Ignite 2.0 Release

Alexey g, Thanks for the update. If IGNITE-4534 and 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

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 : > I've p

Re: Apache Ignite 2.0 Release

I've prepared 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

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 lo

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 wrote: > 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% > 20fixVersi

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%

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 i

Re: Apache Ignite 2.0 Release

Hello community! Denis, issue 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 : > *Denis Magda:* > IGNITE-1192

Re: Apache Ignite 2.0 Release

Yes, I think they have to be released as well. Igniters, who can take over these tasks and make them done by the code freeze? — Denis > On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan wrote: > > *Denis*, we still have 5 issues that are *unassigned*. Are they supposed to > be getting into release

Re: Apache Ignite 2.0 Release

> *Denis Magda:* > 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 a

Re: Apache Ignite 2.0 Release

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 - Rework offheap storage IGNITE-4337 - Intr

Re: Apache Ignite 2.0 Release

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 In short, A

Re: Apache Ignite 2.0 Release

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 wrote: > Igniters, > > What’s the overal

Re: Apache Ignite 2.0 Release

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 threat

Re: Apache Ignite 2.0 Release

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)" with " set(Something...)". This should make configuratio

Re: Apache Ignite 2.0 Release

Vovan, I expect to finalize and merge Spring Data Integration by the code freeze time (April 14th):  IGNITE-1192Provide integration with Spring Data — Denis > On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov wrote: > > Igniters, > > We are ge

Re: Apache Ignite 2.0 Release

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 we

Re: Apache Ignite 2.0 Release

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 N

Re: Apache Ignite 2.0 Release

I merged several important changes today: - IGNITE-3579: Message type should be short - IGNITE-4475: Simplify async API On Fri, Mar 24, 2017 at 2:16 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi Rishi, > > Yes, the fix will be in 2.0. > > -Val > > On Wed, Mar 22, 2017 at 7

Re: Apache Ignite 2.0 Release

Hi Rishi, Yes, the fix will be in 2.0. -Val On Wed, Mar 22, 2017 at 7:32 PM, Rishi Yagnik wrote: > Val knows the issue well, the web session clustering we provide does not > work on spring boot at this point however in previous discussion, Val > mentioned that the fix can be made and released

Re: Apache Ignite 2.0 Release

Denis, All the stuff you've mentioned is merged into H2 master. In Ignite we do some related work though. In addition I work on H2 result set generation improvements and will merge them soon as well. After that we'll try to release H2. Sergi 2017-03-23 6:12 GMT+03:00 Denis Magda : > Refreshed

Re: Apache Ignite 2.0 Release

Refreshed a list of “Required tickets” that, personally, have to be released under 2.0: https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0 Most of them are related to the new memory architecture, SQL improvements, Hibernate 5 support and general API cleanup. Some of SQL ticket

Re: Apache Ignite 2.0 Release

Val knows the issue well, the web session clustering we provide does not work on spring boot at this point however in previous discussion, Val mentioned that the fix can be made and released in 2.0. On Wed, Mar 22, 2017 at 1:01 PM, Dmitriy Setrakyan wrote: > On Wed, Mar 22, 2017 at 10:29 AM, Ris

Re: Apache Ignite 2.0 Release

On Wed, Mar 22, 2017 at 10:29 AM, Rishi Yagnik wrote: > Val, > > do you think we will have a web session clustering in Ignite 2.0 ? > Rishi, to my knowledge, we already have web sessions clustering in Ignite: https://apacheignite-mix.readme.io/docs/web-session-clustering Is this what you are

Re: Apache Ignite 2.0 Release

Val, do you think we will have a web session clustering in Ignite 2.0 ? Thanks, On Wed, Mar 22, 2017 at 12:18 PM, Denis Magda wrote: > Igniters, > > Branch ignite-2.0 was merged to master and removed after that. > > All the commits must go to master. AI 2.0 release branch will be created > in

Re: Apache Ignite 2.0 Release

Thanks, Denis! Looks reasonable to me. On Wed, Mar 22, 2017 at 10:18 AM, Denis Magda wrote: > Igniters, > > Branch ignite-2.0 was merged to master and removed after that. > > All the commits must go to master. AI 2.0 release branch will be created > in a matter of 1-2 weeks based on final code f