[GitHub] ignite pull request #4885: GG-14260 backport IGNITE-9004
GitHub user macrergate opened a pull request: https://github.com/apache/ignite/pull/4885 GG-14260 backport IGNITE-9004 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-14260 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4885.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4885 commit 19bef904d53138609a573b3bc71f83fcc434658e Author: Ivan Rakov Date: 2018-05-31T13:56:14Z IGNITE-8476 AssertionError exception occurs when trying to remove node from baseline under loading (cherry picked from commit 5e6e4e5) commit dc1cc39ffc0cdb2abc2767852883d6c8307cf9ea Author: Anton Kalashnikov Date: 2018-05-31T13:06:52Z IGNITE-8530 fixed onNodeLeft for InitNewCoordinatorFuture - Fixes #4086. Signed-off-by: Alexey Goncharuk (cherry picked from commit 49fe8cd) commit 383f3ad52d20045477fe4fed61d1d56e97ece35d Author: dgladkikh Date: 2018-06-01T15:34:50Z IGNITE-8603 Add JMX-metric to cluster: baseline nodes - Fixes #4060. Signed-off-by: Ivan Rakov (cherry picked from commit 1f6266c) commit a716bbee641a123f313325140ded10dc0c2de9ba Author: Sergey Skudnov Date: 2018-05-14T10:35:14Z IGNITE-8138 Uptime output with days - Fixes #3775. Cherry-picked from dfb0b9ee35afeb6adc546160c37b08a85d869f59 Signed-off-by: dpavlov commit 9c381fd3ef0f75e2fed4562f562904ce5ede6bc3 Author: Ivan Daschinskiy Date: 2018-05-10T11:56:35Z IGNITE-8424 Add directory sorting and skip duplicated config file in order to consistently start nodes. Signed-off-by: Andrey Gura (cherry picked from commit bec3e9b) commit dc8ba0932a944f3e966ebbe2af053488d1fe9b28 Author: Sergey Chugunov Date: 2018-05-04T12:26:02Z IGNITE-8421 new implementation of getChildren method is added tolerating KeeperException.NoNodeException - Fixes #3939. Signed-off-by: dpavlov (cherry-picked from commit #02e9ca993178d4aa648d06cb93ce1a9277eb22b1) commit 0d37bd6749829ce07fbd4b0d2344b62588177628 Author: Ivan Rakov Date: 2018-06-05T11:42:43Z IGNITE-8682 Attempt to configure IGFS in persistent mode without specific data region ends with AssertionError (cherry picked from commit 2fe0a10) commit 0c20c51025e5a550b7f3d8458acae27ec8cdcef5 Author: a-polyakov Date: 2018-06-05T15:49:19Z IGNITE-8602 Add support filter "label null" for control.sh tx utility - Fixes #4073. Signed-off-by: Alexey Goncharuk (cherry picked from commit 3372590) commit 455777d2cd2bd6b83d69dbdbbd7e95b4f375bb75 Author: a-polyakov Date: 2018-06-05T16:01:03Z IGNITE-8467 Fixed filter minSize for transactions utility control.sh. Fixes #4069 (cherry picked from commit d61c068) commit c40f7659f24b6037485a5ac5e1965b0c6bd573bb Author: Sergey Kosarev Date: 2018-06-06T08:19:26Z IGNITE-8587 GridToStringBuilder use ConcurrentHashMap to avoid global locks on classCache - Fixes #4059. Signed-off-by: Alexey Goncharuk (cherry picked from commit ecd8261f1add62099fde39aa7dca49855a866eda) commit af026c7840101e2c57c7dd882baabddb6df2fa82 Author: Ilya Lantukh Date: 2018-06-04T22:24:37Z IGNITE-8693 SQL JOIN between PARTITIONED and REPLICATED cache fails - Fixes #4120. Signed-off-by: Ivan Rakov (cherry picked from commit bc35ce0) commit a84538a9df8ace432411736289ec8371dee215e2 Author: Sergey Kosarev Date: 2018-06-06T09:59:28Z IGNITE-8696 control.sh utility does not show atomicity mode - Fixes #4127. Signed-off-by: Ivan Rakov (cherry picked from commit 78e5d970be74c04b01857123b1a623038aa18440) commit fff8a4cc48ae7d8a47f8911763a71d0d59042d87 Author: Andrey Kuznetsov Date: 2018-06-06T12:02:35Z IGNITE-8642 Added thread dumping to FailureProcessor Signed-off-by: Andrey Gura commit 6ea23844cfb0294a0cf3f3c21787aeff30939bcf Author: Dmitriy Sorokin Date: 2018-06-06T11:34:04Z IGNITE-8311 IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE Signed-off-by: Andrey Gura commit bad52d3843925d831e6d357a4382731751ae6bb7 Author: Ilya Lantukh Date: 2018-06-04T14:07:52Z GG-13862 : Disabled fast eviction. (cherry picked from commit 786633d) commit 6956097ceedd2e3e9edcb627d97e49afb7f0a26d Author: Pavel Kovalenko Date: 2018-06-06T12:24:39Z IGNITE-8482 Skip 2-phase partition release wait in case of activation or dynamic caches start - Fixes #4078. Signed-off-by: Alexey Goncharuk (cherry picked from commit 7c565d2) commit d777c76eadd0a2ccc50f1031c42626b135da5906 Author: Dmitriy Govorukhin Date: 2018-06-06T14:20:18Z IGNITE-8685 Fixed switch segment record size - Fixes #4130.
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Thank you everyone for reviewing the changes. As discussed I have removed the FlinkIgniteSourceSelfExample and also verified that FlinkIgniteSourceSelfTestSuite is part of Ignite Streamers in Team City. Please let me know if any further changes are required. Alex , will you please review and let me know if the PR looks good? Regards, Saikat On Mon, Oct 1, 2018 at 11:58 AM Nikolay Izhikov wrote: > Hello, Andrey. > > Yes, I know it. > I've looked at the PR befor mailing :) > > Do you think we can include this improvement to the 2.7 release? > Do you have time to assist Saikat with TC setup and other tasks? > > > В Пн, 01/10/2018 в 19:54 +0300, Andrey Mashenkov пишет: > > Dmitry, Nikolay, > > > > Ignite-3303 is a new Ignite module and there is no changes related to > core or other existed modules. > > So, PR should not affected existed functional ity and can be safely > merged. > > > > Thanks. > > > > > > пн, 1 окт. 2018 г., 16:04 Dmitriy Pavlov : > > > Hi Saikat, > > > > > > I don't mind merging to master, but I have concern if it will go to > 2.7. In > > > the separate discussion, we agreed on code freeze should happen during > last > > > weekend, September, 30. > > > > > > So it is now up to community and release manager to decide if fix > should go > > > to the upcoming release. Usually, after the freeze, only bug/test > fixes can > > > be merged to release branch. > > > > > > Hi Nikolay, > > > > > > could you please announce that code freeze happened? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > пн, 1 окт. 2018 г. в 3:58, Saikat Maitra : > > > > > > > Hi Alex, Nicolay > > > > > > > > As discussed with Andrew the changes looks good. Would it be ok to > merge > > > > this change to master considering the 2.7 release plan? > > > > > > > > Regards, > > > > Saikat > > > > > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra < > saikat.mai...@gmail.com> > > > > wrote: > > > > > > > > > Thank you Andrew > > > > > > > > > > Regards, > > > > > Saikat > > > > > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > > > andrey.mashen...@gmail.com> wrote: > > > > > > > > > >> Hi Saikat, > > > > >> > > > > >> Sorry for late answer. I've checked changes a day ago. Now, looks > good. > > > > >> Hope, it will be merged soon. > > > > >> > > > > >> Alex, would you please merge PR to master. > > > > >> > > > > >> сб, 29 сент. 2018 г., 2:29 Saikat Maitra >: > > > > >> > > > > >> > Hi Andrew, > > > > >> > > > > > >> > I have updated the changes. > > > > >> > > > > > >> > Can you please review and share feedback. > > > > >> > > > > > >> > Regards > > > > >> > Saikat > > > > >> > > > > > >> > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > > > > saikat.mai...@gmail.com> > > > > >> > wrote: > > > > >> > > > > > >> > > Hi Andrew > > > > >> > > > > > > >> > > > > > > >> > > I have updated the changes. > > > > >> > > > > > > >> > > > > > > >> > > Can you please review and share feedback. > > > > >> > > > > > > >> > > > > > > >> > > Regards > > > > >> > > Saikat > > > > >> > > > > > > >> > > > > > > >> > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > > >> saikat.mai...@gmail.com> > > > > >> > > wrote: > > > > >> > > > > > > >> > >> Hi Andrew, > > > > >> > >> > > > > >> > >> I have updated the tests and also added java docs. > > > > >> > >> > > > > >> > >> Can you please review and share feedback. > > > > >> > >> > > > > >> > >> > > > > >> > >> Regards > > > > >> > >> Saikat > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > > >> > saikat.mai...@gmail.com> > > > > >> > >> wrote: > > > > >> > >> > > > > >> > >>> Hi Andrew, > > > > >> > >>> > > > > >> > >>> I have updated the tests and also added java docs. > > > > >> > >>> > > > > >> > >>> Please review and share feedback. > > > > >> > >>> > > > > >> > >>> Regards > > > > >> > >>> Saikat > > > > >> > >>> > > > > >> > >>> > > > > >> > >>> On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > > >> saikat.mai...@gmail.com > > > > >> > > > > > > >> > >>> wrote: > > > > >> > >>> > > > > >> > Hi Andrew, Alexey > > > > >> > > > > > >> > I have incorporated the review changes. > > > > >> > > > > > >> > I have also refactored the CacheEventSerializer class and > moved > > > > it > > > > >> to > > > > >> > test folder because it is used only in the > > > > >> > FlinkIgniteSourceSelfExample and > > > > >> > not required for IgniteSource. > > > > >> > > > > > >> > Build links > > > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;; > > > > >> > > > > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821774; > ; > > > > >> > > > > > >> > Please review and share feedback. > > > > >> > > > > > >> > Regards > > > > >> > Saikat > > > > >> > > > > > >> > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > > >> > saikat.mai...@gmail.com> > > > > >> > wrote:
[MTCGA]: new failures in builds [1981173] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testDeactivateFailover3 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=9007817803620810671=%3Cdefault%3E=testDetails *Recently contributed test failed in master IgniteClusterActivateDeactivateTestWithPersistenceAndMemoryReuse.testActivateFailover3 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9220444903810360729=%3Cdefault%3E=testDetails Changes may lead to failure were done by - alexey.scherbakoff http://ci.ignite.apache.org/viewModification.html?modId=833290=false - maxmuzaf http://ci.ignite.apache.org/viewModification.html?modId=833287=false - av http://ci.ignite.apache.org/viewModification.html?modId=833262=false - jokserfn http://ci.ignite.apache.org/viewModification.html?modId=833251=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 04:49:14 02-10-2018
[jira] [Created] (IGNITE-9758) Document data injection via the REST API
Pavel Petroshenko created IGNITE-9758:
-
Summary: Document data injection via the REST API
Key: IGNITE-9758
URL: https://issues.apache.org/jira/browse/IGNITE-9758
Project: Ignite
Issue Type: Task
Components: documentation
Affects Versions: 2.6
Reporter: Pavel Petroshenko
There should a documentation on how to post data via the REST API.
Just to capture what was proposed by [~ilyak] over email:
{quote}REST API will convert complex BinaryObjects into JSON by default. But to
put such objects via REST you will need to define your own
ConnectorMessageInterceptor and plug it in. You will need to define string to
entity mapping in onReceive. You can leave onSend returning arg.
This interface should be used:
[https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ConnectorMessageInterceptor.html].
You need to put it into ConnectorConfiguration, which you should put into
IgniteConfiguration.{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: Apache Ignite 2.7 release
Thanks, got it. On Mon, Oct 1, 2018 at 1:14 PM Dmitriy Pavlov wrote: > Here I agree with Vladimir. Furthermore, I do my absolute best to finalize > all reviews in all 2.7 tickets I'm related to. I think most of the > contributors doing the same. > > пн, 1 окт. 2018 г. в 23:03, Vladimir Ozerov : > > > This is precisely the scope we have at the moment. All these tickets were > > considered carefully on whether to include them into AI 2.7 scope. I > would > > say that 10-15% of current tickets may be moved furhter. > > > > Third of current tickets are features on their final review stages (e.g. > > TDE, MVCC invoke, TensorFlow, Thin Clients), another big part is > > stabilization tickets (mainly - various test failures), and another big > > part is infrastructure (adopting new modules, Java 9+ support, etc.). So > > despite big absolute number, most of these tickets are grouped around > > several big areas, and overall progress over this week should be very > good. > > > > On Mon, Oct 1, 2018 at 9:50 PM Dmitriy Setrakyan > > wrote: > > > > > If this filter is for 2.7 release, then I do not believe all these > > tickets > > > will be closed. It would be nice to leave only "must-have" tickets in > 2.7 > > > and move the rest to 2.8. > > > > > > D. > > > > > > On Mon, Oct 1, 2018 at 11:02 AM Vladimir Ozerov > > > wrote: > > > > > > > Igniters, > > > > > > > > Please use this filter, as it properly handles tickets without > > > components: > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > On Mon, Oct 1, 2018 at 6:18 PM Nikolay Izhikov > > > > wrote: > > > > > > > > > Hello, Igniters. > > > > > > > > > > I announce scope freeze for an Apache Ignite 2.7 release. > > > > > > > > > > It means: > > > > > > > > > > 1. We add to 2.7 only critical bugs. > > > > > 2. We merge to 2.7 branch only previously announces features. > > > > > 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO > > > OCTOBER > > > > > 10*. > > > > > So the *October 10 is DEADLINE* for new features. > > > > > > > > > > Thoughts? > > > > > > > > > > For now we have 34 In Progress tickets planned to 2.7 version [1]. > > > > > So is you assigned to any of this ticker friendly reminder #1, *the > > > > > deadline is near :)*. > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > > > > > > > > > > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > > > > > > Agree with Andrey. > > > > > > > > > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > > > > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov < > stku...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > > Igniters, > > > > > > > > > > > > > > There is an inaccuracy in critical worker termination > detection, > > > and > > > > > I'm > > > > > > > working on a fix right now, see [1]. Also, we have trivial yet > > > > > important > > > > > > > fix [2], this one is ready to merge. > > > > > > > > > > > > > > I deem both should get to 2.7. Any objections? > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > > > > > > > > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov < > > dpavlov@gmail.com > > > >: > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > We can consider this thread as an almost healthy discussion > > about > > > > SG > > > > > > > > inclusion to 2.7. > > > > > > > > > > > > > > > > For the future, I encourage all Igniters to discuss things > > before > > > > > agreement > > > > > > > > on dev.list instead of trying to log 'some pre-build > > agreements' > > > > > here. BTW > > > > > > > > such logged 'agreements' are not always valid. > > > > > > > > > > > > > > > > Dev list is not a log of community actions; it is the > principal > > > > > place where > > > > > > > > discussion runs. I sincerely hope all similar decisions will > be > > > > > building on > > > > > > > > the dev list. > > > > > > > > > > > > > > > > Sincerely, > > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov < > > > nizhi...@apache.org > > > > >: > > > > > > > > > > > > > > > > > Hello, guys. > > > > > > > > > > > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > > > > > > > > > > > В Сб, 29/09/2018 в
Re: Apache Ignite 2.7 release
Here I agree with Vladimir. Furthermore, I do my absolute best to finalize all reviews in all 2.7 tickets I'm related to. I think most of the contributors doing the same. пн, 1 окт. 2018 г. в 23:03, Vladimir Ozerov : > This is precisely the scope we have at the moment. All these tickets were > considered carefully on whether to include them into AI 2.7 scope. I would > say that 10-15% of current tickets may be moved furhter. > > Third of current tickets are features on their final review stages (e.g. > TDE, MVCC invoke, TensorFlow, Thin Clients), another big part is > stabilization tickets (mainly - various test failures), and another big > part is infrastructure (adopting new modules, Java 9+ support, etc.). So > despite big absolute number, most of these tickets are grouped around > several big areas, and overall progress over this week should be very good. > > On Mon, Oct 1, 2018 at 9:50 PM Dmitriy Setrakyan > wrote: > > > If this filter is for 2.7 release, then I do not believe all these > tickets > > will be closed. It would be nice to leave only "must-have" tickets in 2.7 > > and move the rest to 2.8. > > > > D. > > > > On Mon, Oct 1, 2018 at 11:02 AM Vladimir Ozerov > > wrote: > > > > > Igniters, > > > > > > Please use this filter, as it properly handles tickets without > > components: > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > On Mon, Oct 1, 2018 at 6:18 PM Nikolay Izhikov > > > wrote: > > > > > > > Hello, Igniters. > > > > > > > > I announce scope freeze for an Apache Ignite 2.7 release. > > > > > > > > It means: > > > > > > > > 1. We add to 2.7 only critical bugs. > > > > 2. We merge to 2.7 branch only previously announces features. > > > > 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO > > OCTOBER > > > > 10*. > > > > So the *October 10 is DEADLINE* for new features. > > > > > > > > Thoughts? > > > > > > > > For now we have 34 In Progress tickets planned to 2.7 version [1]. > > > > So is you assigned to any of this ticker friendly reminder #1, *the > > > > deadline is near :)*. > > > > > > > > [1] > > > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > > > > > > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > > > > > Agree with Andrey. > > > > > > > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > > > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov > > > > > wrote: > > > > > > > > > > > > Igniters, > > > > > > > > > > > > There is an inaccuracy in critical worker termination detection, > > and > > > > I'm > > > > > > working on a fix right now, see [1]. Also, we have trivial yet > > > > important > > > > > > fix [2], this one is ready to merge. > > > > > > > > > > > > I deem both should get to 2.7. Any objections? > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > > > > > > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov < > dpavlov@gmail.com > > >: > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > We can consider this thread as an almost healthy discussion > about > > > SG > > > > > > > inclusion to 2.7. > > > > > > > > > > > > > > For the future, I encourage all Igniters to discuss things > before > > > > agreement > > > > > > > on dev.list instead of trying to log 'some pre-build > agreements' > > > > here. BTW > > > > > > > such logged 'agreements' are not always valid. > > > > > > > > > > > > > > Dev list is not a log of community actions; it is the principal > > > > place where > > > > > > > discussion runs. I sincerely hope all similar decisions will be > > > > building on > > > > > > > the dev list. > > > > > > > > > > > > > > Sincerely, > > > > > > > Dmitriy Pavlov > > > > > > > > > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov < > > nizhi...@apache.org > > > >: > > > > > > > > > > > > > > > Hello, guys. > > > > > > > > > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > > > > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > > > > > > I fully support Dmitry's concerns. I do not see a single > > chance > > > > for > > > > > > > > > > > > > > > > Service > > > > > > > > > Grid to be included into 2.7 scope, but we are still > keeping > > > hope > > > > > > > > > > > > > > alive. > > > > > > > > > What for? Our experience shows, that any feature
Re: Apache Ignite 2.7 release
This is precisely the scope we have at the moment. All these tickets were considered carefully on whether to include them into AI 2.7 scope. I would say that 10-15% of current tickets may be moved furhter. Third of current tickets are features on their final review stages (e.g. TDE, MVCC invoke, TensorFlow, Thin Clients), another big part is stabilization tickets (mainly - various test failures), and another big part is infrastructure (adopting new modules, Java 9+ support, etc.). So despite big absolute number, most of these tickets are grouped around several big areas, and overall progress over this week should be very good. On Mon, Oct 1, 2018 at 9:50 PM Dmitriy Setrakyan wrote: > If this filter is for 2.7 release, then I do not believe all these tickets > will be closed. It would be nice to leave only "must-have" tickets in 2.7 > and move the rest to 2.8. > > D. > > On Mon, Oct 1, 2018 at 11:02 AM Vladimir Ozerov > wrote: > > > Igniters, > > > > Please use this filter, as it properly handles tickets without > components: > > > > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > On Mon, Oct 1, 2018 at 6:18 PM Nikolay Izhikov > > wrote: > > > > > Hello, Igniters. > > > > > > I announce scope freeze for an Apache Ignite 2.7 release. > > > > > > It means: > > > > > > 1. We add to 2.7 only critical bugs. > > > 2. We merge to 2.7 branch only previously announces features. > > > 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO > OCTOBER > > > 10*. > > > So the *October 10 is DEADLINE* for new features. > > > > > > Thoughts? > > > > > > For now we have 34 In Progress tickets planned to 2.7 version [1]. > > > So is you assigned to any of this ticker friendly reminder #1, *the > > > deadline is near :)*. > > > > > > [1] > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > > > > Agree with Andrey. > > > > > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov > > > wrote: > > > > > > > > > > Igniters, > > > > > > > > > > There is an inaccuracy in critical worker termination detection, > and > > > I'm > > > > > working on a fix right now, see [1]. Also, we have trivial yet > > > important > > > > > fix [2], this one is ready to merge. > > > > > > > > > > I deem both should get to 2.7. Any objections? > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > > > > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov >: > > > > > > > > > > > Folks, > > > > > > > > > > > > We can consider this thread as an almost healthy discussion about > > SG > > > > > > inclusion to 2.7. > > > > > > > > > > > > For the future, I encourage all Igniters to discuss things before > > > agreement > > > > > > on dev.list instead of trying to log 'some pre-build agreements' > > > here. BTW > > > > > > such logged 'agreements' are not always valid. > > > > > > > > > > > > Dev list is not a log of community actions; it is the principal > > > place where > > > > > > discussion runs. I sincerely hope all similar decisions will be > > > building on > > > > > > the dev list. > > > > > > > > > > > > Sincerely, > > > > > > Dmitriy Pavlov > > > > > > > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov < > nizhi...@apache.org > > >: > > > > > > > > > > > > > Hello, guys. > > > > > > > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > > > > > I fully support Dmitry's concerns. I do not see a single > chance > > > for > > > > > > > > > > > > > > Service > > > > > > > > Grid to be included into 2.7 scope, but we are still keeping > > hope > > > > > > > > > > > > alive. > > > > > > > > What for? Our experience shows, that any feature involving > > > consensus > > > > > > > > algorithms typically take weeks to be finalized after initial > > > public > > > > > > > > review. Yes, it is possible that at some day in October we > will > > > see it > > > > > > > > completed, but what about testing? What about regressions > with > > > other > > > > > > > > components? Let me reming you that from Monday a lot of > efforts > > > will be > > > > > > > > > > > > > > put > > > > > > > > into project stabilization. This is the sole purpose of that > >
Re: Published articles on Data streaming in Dzone and Tech@Target
Thanks, Saikat, great blog! On Sat, Sep 29, 2018 at 7:13 AM Saikat Maitra wrote: > Hi, > > We have published an article on Data streaming at Dzone. Thank you Prachi > for help for publishing the article > > > https://dzone.com/articles/data-streaming-using-apache-flink-and-apache-ignit > > Also wrote an post at Tech@Target about how I started with Apache Ignite > > > https://tech.target.com/2018/09/14/data-streaming-using-apache-flink-and-apache-ignite.html > > Please let me know if you have any feedback. > > Regards, > Saikat >
Re: Apache Ignite 2.7 release
If this filter is for 2.7 release, then I do not believe all these tickets will be closed. It would be nice to leave only "must-have" tickets in 2.7 and move the rest to 2.8. D. On Mon, Oct 1, 2018 at 11:02 AM Vladimir Ozerov wrote: > Igniters, > > Please use this filter, as it properly handles tickets without components: > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > On Mon, Oct 1, 2018 at 6:18 PM Nikolay Izhikov > wrote: > > > Hello, Igniters. > > > > I announce scope freeze for an Apache Ignite 2.7 release. > > > > It means: > > > > 1. We add to 2.7 only critical bugs. > > 2. We merge to 2.7 branch only previously announces features. > > 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO OCTOBER > > 10*. > > So the *October 10 is DEADLINE* for new features. > > > > Thoughts? > > > > For now we have 34 In Progress tickets planned to 2.7 version [1]. > > So is you assigned to any of this ticker friendly reminder #1, *the > > deadline is near :)*. > > > > [1] > > > > > https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > > > Agree with Andrey. > > > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov > > wrote: > > > > > > > > Igniters, > > > > > > > > There is an inaccuracy in critical worker termination detection, and > > I'm > > > > working on a fix right now, see [1]. Also, we have trivial yet > > important > > > > fix [2], this one is ready to merge. > > > > > > > > I deem both should get to 2.7. Any objections? > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov : > > > > > > > > > Folks, > > > > > > > > > > We can consider this thread as an almost healthy discussion about > SG > > > > > inclusion to 2.7. > > > > > > > > > > For the future, I encourage all Igniters to discuss things before > > agreement > > > > > on dev.list instead of trying to log 'some pre-build agreements' > > here. BTW > > > > > such logged 'agreements' are not always valid. > > > > > > > > > > Dev list is not a log of community actions; it is the principal > > place where > > > > > discussion runs. I sincerely hope all similar decisions will be > > building on > > > > > the dev list. > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov >: > > > > > > > > > > > Hello, guys. > > > > > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > > > > I fully support Dmitry's concerns. I do not see a single chance > > for > > > > > > > > > > > > Service > > > > > > > Grid to be included into 2.7 scope, but we are still keeping > hope > > > > > > > > > > alive. > > > > > > > What for? Our experience shows, that any feature involving > > consensus > > > > > > > algorithms typically take weeks to be finalized after initial > > public > > > > > > > review. Yes, it is possible that at some day in October we will > > see it > > > > > > > completed, but what about testing? What about regressions with > > other > > > > > > > components? Let me reming you that from Monday a lot of efforts > > will be > > > > > > > > > > > > put > > > > > > > into project stabilization. This is the sole purpose of that > > > > > > > > > > pre-release > > > > > > > phase. Accepting a patch with deep rework of Ignite internals > in > > the > > > > > > > > > > > > middle > > > > > > > of that process, means that our effrots will be lost. This is > > simply a > > > > > > > matter of respect to contributor's time. > > > > > > > > > > > > > > Another problem is that this false hope puts us at rush. Rush > > during > > > > > > > design, development, review, testing. Result is known - bad > > features, > > > > > > > > > > > > which > > > > > > > makes damage to the project. > > > > > > > > > > > > > > So my question is - why don't we just want to move it to AI 2.8 > > right > > > > > > > > > > > > now? > > > > > > > Feature is big, feature is very far from being ready. This > simple > > > > > > > > > > action > > > > > > > immediately shifts the focus from dates to quality of the > > product, and > > > > > > > remove any risks that potential merge will defeat stabilization > >
[GitHub] ignite pull request #4883: Ignite 2.4.11
GitHub user Max-Pudov opened a pull request: https://github.com/apache/ignite/pull/4883 Ignite 2.4.11 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.11 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4883.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4883 commit cdbf963efc6bad7520fa174a47207fd0b34fe9f2 Author: Anton Kalashnikov Date: 2018-03-26T11:57:11Z GG-13638 move setting compatibilityMode to head of collectGridNodeData - Fixes #3665. Signed-off-by: Alexey Goncharuk (cherry picked from commit df8c823) commit 2280e55a228d37ad324d5d2fc7248f2b0c1b46f8 Author: Alexey Popov Date: 2018-03-26T14:00:07Z IGNITE-7928: .NET: Fixed hang caused by mishandled exception during custom cache store deserialization. This closes #3690. commit e0a24a1014a19fb3bd698b83d9a1664a3b9a06b9 Author: Pavel Tupitsyn Date: 2018-01-26T08:48:14Z IGNITE-7530 .NET: Fix GetAll memory usage and performance in binary mode This closes #3436 commit e721130d85cf31775d94a004164a4287e3c2f68f Author: Alexey Popov Date: 2018-03-06T17:47:18Z IGNITE-7889: .NET: LINQ: Fix GroupBy with Where This closes #3608 commit 0534edaedcc84473c8c26c9d19ad09ef66210246 Author: Pavel Tupitsyn Date: 2018-03-27T07:51:49Z IGNITE-8034 .NET: Add IgniteConfiguration.AuthenticationEnabled This closes #3696 commit 9478c5a7bd2d97252ab0de72c8b96e7eadc651de Author: devozerov Date: 2018-03-27T10:58:54Z Merge branch 'ignite-2.4.4' into ignite-2.4-master # Conflicts: # modules/core/src/main/java/org/apache/ignite/internal/processors/cluster/GridClusterStateProcessor.java commit 3a0dc509fa44c6b5d5204a06ffa8485e530ca933 Author: Valentin Kulichenko Date: 2018-03-20T02:20:20Z Added new test to suite Signed-off-by: Valentin Kulichenko (cherry picked from commit baf08bc9501676e418dab2431211a659ae421d25) commit f1fec0e87b5d37850636c04ddf72655fc8ee951f Author: Alexey Popov Date: 2018-03-26T14:00:07Z IGNITE-7928: .NET: Fixed hang caused by mishandled exception during custom cache store deserialization. This closes #3690. commit 926a2ee11873edc090c1fc06781d369ffae46d44 Author: Denis Mekhanikov Date: 2018-03-20T02:19:35Z IGNITE-7794 - Share persisted marshaller mappings when connecting - Fixes #3620. Signed-off-by: Valentin Kulichenko (cherry picked from commit c4ccf55dd6eb22102c56e211812eb4ccc206f4a7) commit 76388519f029d425a7080a4638ff9b4f90bddbd9 Author: Pavel Kovalenko Date: 2018-03-21T14:22:56Z IGNITE-6113 Fixed partition eviction preventing exchange completion - Fixes #3445. Signed-off-by: Alexey Goncharuk (cherry picked from commit 6dc5804af6dda90ca210a39d622964d78e3890f1) commit 180542911e7a113aeb4a7074a864e008f60e070a Author: Pavel Kovalenko Date: 2018-03-21T14:32:51Z IGNITE-6113 Fixed version handling. commit bfdb5bcdd971b2afe48ab6878c68f5728acffdf2 Author: Pavel Kovalenko Date: 2018-03-06T18:22:40Z IGNITE-6113 Return back old implementation instead of 'removeIf' - Fixes #3609. Signed-off-by: Alexey Goncharuk (cherry picked from commit 8c3731e83296e1750c7c098b283c3fd8584b1be4) commit d0aec4846ad55ea59b5688ce9c935d31cd468e9c Author: Anton Kalashnikov Date: 2018-03-21T15:53:15Z GG-13631 fix GridDhtPartitionDemandLegacyMessage (cherry picked from commit ffbc56e) commit fb54691290128be81be641c3c6206f0ca2569274 Author: Sergey Kosarev Date: 2018-03-21T04:11:01Z IGNITE-7864 Control utility: Added confirm on dangerous operations. commit e331e92a906d31b97a9e2c6548097c715e4245f5 Author: devozerov Date: 2018-03-29T10:25:50Z Merge branch 'ignite-2.4.4' into ignite-2.4-master commit dfc268dd62236a32f8bf90e063edd57666c97f92 Author: Alexey Kukushkin Date: 2018-03-29T10:21:36Z IGNITE-7421: Java thin client. commit 2c39ec5dda1a05d03e1317b740fbafee8dd874f0 Author: devozerov Date: 2018-03-29T10:46:47Z Merge branch 'ignite-2.4.4' into ignite-2.4-master commit a58bc16543e72dfc3a2b97c50506cd532d4d9dee Author: devozerov Date: 2018-03-29T12:21:46Z IGNITE-7421: Reverted invalid server-side authentication. commit e7ec84a17c5999441f1731aad64f540fd2eda279 Author: devozerov Date: 2018-03-29T12:23:26Z Merge branch 'ignite-2.4.4' into ignite-2.4-master commit 188279848a75d6458b9441d65917fb628834355e Author: devozerov Date: 2018-03-30T09:04:33Z IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations. This closes #3496. commit b4320072ca75e5b11bbeeb033c2f60f31f4855f9 Author: devozerov Date: 2018-03-30T09:18:10Z Merge remote-tracking branch 'upstream/ignite-2.4.4' into ignite-2.4.4 commit
Re: Apache Ignite 2.7 release
Igniters, Please use this filter, as it properly handles tickets without components: https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 On Mon, Oct 1, 2018 at 6:18 PM Nikolay Izhikov wrote: > Hello, Igniters. > > I announce scope freeze for an Apache Ignite 2.7 release. > > It means: > > 1. We add to 2.7 only critical bugs. > 2. We merge to 2.7 branch only previously announces features. > 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO OCTOBER > 10*. > So the *October 10 is DEADLINE* for new features. > > Thoughts? > > For now we have 34 In Progress tickets planned to 2.7 version [1]. > So is you assigned to any of this ticker friendly reminder #1, *the > deadline is near :)*. > > [1] > > https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > > Agree with Andrey. > > > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov > wrote: > > > > > > Igniters, > > > > > > There is an inaccuracy in critical worker termination detection, and > I'm > > > working on a fix right now, see [1]. Also, we have trivial yet > important > > > fix [2], this one is ready to merge. > > > > > > I deem both should get to 2.7. Any objections? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov : > > > > > > > Folks, > > > > > > > > We can consider this thread as an almost healthy discussion about SG > > > > inclusion to 2.7. > > > > > > > > For the future, I encourage all Igniters to discuss things before > agreement > > > > on dev.list instead of trying to log 'some pre-build agreements' > here. BTW > > > > such logged 'agreements' are not always valid. > > > > > > > > Dev list is not a log of community actions; it is the principal > place where > > > > discussion runs. I sincerely hope all similar decisions will be > building on > > > > the dev list. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov : > > > > > > > > > Hello, guys. > > > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > > > I fully support Dmitry's concerns. I do not see a single chance > for > > > > > > > > > > Service > > > > > > Grid to be included into 2.7 scope, but we are still keeping hope > > > > > > > > alive. > > > > > > What for? Our experience shows, that any feature involving > consensus > > > > > > algorithms typically take weeks to be finalized after initial > public > > > > > > review. Yes, it is possible that at some day in October we will > see it > > > > > > completed, but what about testing? What about regressions with > other > > > > > > components? Let me reming you that from Monday a lot of efforts > will be > > > > > > > > > > put > > > > > > into project stabilization. This is the sole purpose of that > > > > > > > > pre-release > > > > > > phase. Accepting a patch with deep rework of Ignite internals in > the > > > > > > > > > > middle > > > > > > of that process, means that our effrots will be lost. This is > simply a > > > > > > matter of respect to contributor's time. > > > > > > > > > > > > Another problem is that this false hope puts us at rush. Rush > during > > > > > > design, development, review, testing. Result is known - bad > features, > > > > > > > > > > which > > > > > > makes damage to the project. > > > > > > > > > > > > So my question is - why don't we just want to move it to AI 2.8 > right > > > > > > > > > > now? > > > > > > Feature is big, feature is very far from being ready. This simple > > > > > > > > action > > > > > > immediately shifts the focus from dates to quality of the > product, and > > > > > > remove any risks that potential merge will defeat stabilization > effrots > > > > > > > > > > of > > > > > > other contributors. > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 29, 2018 at 8:32 AM Vyacheslav Daradur < > > > > > > > > daradu...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Dmitriy, > > > > > > > > > > > > > > Hot redeployment and versioning will not be implemented in > phase 1, > > > > > > > but it is scheduled once it is finished. > > > > > > > > > > > > > > Here is an umbrella ticket [1] to track phase 1 scope. > > > > > > > > > > >
[jira] [Created] (IGNITE-9757) С++: DetachCurrentThread is never called, causing Java thread leak
Pavel Tupitsyn created IGNITE-9757: -- Summary: С++: DetachCurrentThread is never called, causing Java thread leak Key: IGNITE-9757 URL: https://issues.apache.org/jira/browse/IGNITE-9757 Project: Ignite Issue Type: Bug Components: platforms Reporter: Pavel Tupitsyn Assignee: Igor Sapego JNI method AttrachCurrentThread must be called on every thread that performs JNI calls. This causes Thread object to be created on Java side, with a bunch of thread-local values (both managed and unmanaged). To clean this up we must call DetachCurrentThread JNI method. Ignite C++ seems to never do this. Same issue as IGNITE-9638 for .NET, known to cause OOM in a scenario where lots of threads are created and destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Hello, Andrey. Yes, I know it. I've looked at the PR befor mailing :) Do you think we can include this improvement to the 2.7 release? Do you have time to assist Saikat with TC setup and other tasks? В Пн, 01/10/2018 в 19:54 +0300, Andrey Mashenkov пишет: > Dmitry, Nikolay, > > Ignite-3303 is a new Ignite module and there is no changes related to core or > other existed modules. > So, PR should not affected existed functional ity and can be safely merged. > > Thanks. > > > пн, 1 окт. 2018 г., 16:04 Dmitriy Pavlov : > > Hi Saikat, > > > > I don't mind merging to master, but I have concern if it will go to 2.7. In > > the separate discussion, we agreed on code freeze should happen during last > > weekend, September, 30. > > > > So it is now up to community and release manager to decide if fix should go > > to the upcoming release. Usually, after the freeze, only bug/test fixes can > > be merged to release branch. > > > > Hi Nikolay, > > > > could you please announce that code freeze happened? > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 1 окт. 2018 г. в 3:58, Saikat Maitra : > > > > > Hi Alex, Nicolay > > > > > > As discussed with Andrew the changes looks good. Would it be ok to merge > > > this change to master considering the 2.7 release plan? > > > > > > Regards, > > > Saikat > > > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > > > wrote: > > > > > > > Thank you Andrew > > > > > > > > Regards, > > > > Saikat > > > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > > andrey.mashen...@gmail.com> wrote: > > > > > > > >> Hi Saikat, > > > >> > > > >> Sorry for late answer. I've checked changes a day ago. Now, looks good. > > > >> Hope, it will be merged soon. > > > >> > > > >> Alex, would you please merge PR to master. > > > >> > > > >> сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > > > >> > > > >> > Hi Andrew, > > > >> > > > > >> > I have updated the changes. > > > >> > > > > >> > Can you please review and share feedback. > > > >> > > > > >> > Regards > > > >> > Saikat > > > >> > > > > >> > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > > > saikat.mai...@gmail.com> > > > >> > wrote: > > > >> > > > > >> > > Hi Andrew > > > >> > > > > > >> > > > > > >> > > I have updated the changes. > > > >> > > > > > >> > > > > > >> > > Can you please review and share feedback. > > > >> > > > > > >> > > > > > >> > > Regards > > > >> > > Saikat > > > >> > > > > > >> > > > > > >> > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > >> saikat.mai...@gmail.com> > > > >> > > wrote: > > > >> > > > > > >> > >> Hi Andrew, > > > >> > >> > > > >> > >> I have updated the tests and also added java docs. > > > >> > >> > > > >> > >> Can you please review and share feedback. > > > >> > >> > > > >> > >> > > > >> > >> Regards > > > >> > >> Saikat > > > >> > >> > > > >> > >> > > > >> > >> > > > >> > >> > > > >> > >> On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > >> > saikat.mai...@gmail.com> > > > >> > >> wrote: > > > >> > >> > > > >> > >>> Hi Andrew, > > > >> > >>> > > > >> > >>> I have updated the tests and also added java docs. > > > >> > >>> > > > >> > >>> Please review and share feedback. > > > >> > >>> > > > >> > >>> Regards > > > >> > >>> Saikat > > > >> > >>> > > > >> > >>> > > > >> > >>> On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > >> saikat.mai...@gmail.com > > > >> > > > > > >> > >>> wrote: > > > >> > >>> > > > >> > Hi Andrew, Alexey > > > >> > > > > >> > I have incorporated the review changes. > > > >> > > > > >> > I have also refactored the CacheEventSerializer class and moved > > > it > > > >> to > > > >> > test folder because it is used only in the > > > >> > FlinkIgniteSourceSelfExample and > > > >> > not required for IgniteSource. > > > >> > > > > >> > Build links > > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;; > > > >> > > > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821774;; > > > >> > > > > >> > Please review and share feedback. > > > >> > > > > >> > Regards > > > >> > Saikat > > > >> > > > > >> > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > >> > saikat.mai...@gmail.com> > > > >> > wrote: > > > >> > > > > >> > > Hi Alexey, > > > >> > > > > > >> > > Thank you for reviewing the changes and sharing feedback, I am > > > >> > > updating the PR. I will share the changes shortly. > > > >> > > > > > >> > > Regards, > > > >> > > Saikat > > > >> > > > > > >> > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > > > >> > > alexey.goncha...@gmail.com> wrote: > > > >> > > > > > >> > >> Hello Saikat, > > > >> > >> > > > >> > >> I see a few fellow Igniters added some comments to your PR > > > >> > (including > > > >> > >> me). > > > >> > >> I believe the PR can be merged after you address them. > > > >> > >> > > > >> > >> Thanks, > > > >> > >>
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Dmitry, Nikolay, Ignite-3303 is a new Ignite module and there is no changes related to core or other existed modules. So, PR should not affected existed functional ity and can be safely merged. Thanks. пн, 1 окт. 2018 г., 16:04 Dmitriy Pavlov : > Hi Saikat, > > I don't mind merging to master, but I have concern if it will go to 2.7. In > the separate discussion, we agreed on code freeze should happen during last > weekend, September, 30. > > So it is now up to community and release manager to decide if fix should go > to the upcoming release. Usually, after the freeze, only bug/test fixes can > be merged to release branch. > > Hi Nikolay, > > could you please announce that code freeze happened? > > Sincerely, > Dmitriy Pavlov > > пн, 1 окт. 2018 г. в 3:58, Saikat Maitra : > > > Hi Alex, Nicolay > > > > As discussed with Andrew the changes looks good. Would it be ok to merge > > this change to master considering the 2.7 release plan? > > > > Regards, > > Saikat > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > > wrote: > > > > > Thank you Andrew > > > > > > Regards, > > > Saikat > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > andrey.mashen...@gmail.com> wrote: > > > > > >> Hi Saikat, > > >> > > >> Sorry for late answer. I've checked changes a day ago. Now, looks > good. > > >> Hope, it will be merged soon. > > >> > > >> Alex, would you please merge PR to master. > > >> > > >> сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > > >> > > >> > Hi Andrew, > > >> > > > >> > I have updated the changes. > > >> > > > >> > Can you please review and share feedback. > > >> > > > >> > Regards > > >> > Saikat > > >> > > > >> > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > > saikat.mai...@gmail.com> > > >> > wrote: > > >> > > > >> > > Hi Andrew > > >> > > > > >> > > > > >> > > I have updated the changes. > > >> > > > > >> > > > > >> > > Can you please review and share feedback. > > >> > > > > >> > > > > >> > > Regards > > >> > > Saikat > > >> > > > > >> > > > > >> > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > >> saikat.mai...@gmail.com> > > >> > > wrote: > > >> > > > > >> > >> Hi Andrew, > > >> > >> > > >> > >> I have updated the tests and also added java docs. > > >> > >> > > >> > >> Can you please review and share feedback. > > >> > >> > > >> > >> > > >> > >> Regards > > >> > >> Saikat > > >> > >> > > >> > >> > > >> > >> > > >> > >> > > >> > >> On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > >> > saikat.mai...@gmail.com> > > >> > >> wrote: > > >> > >> > > >> > >>> Hi Andrew, > > >> > >>> > > >> > >>> I have updated the tests and also added java docs. > > >> > >>> > > >> > >>> Please review and share feedback. > > >> > >>> > > >> > >>> Regards > > >> > >>> Saikat > > >> > >>> > > >> > >>> > > >> > >>> On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > >> saikat.mai...@gmail.com > > >> > > > > >> > >>> wrote: > > >> > >>> > > >> > Hi Andrew, Alexey > > >> > > > >> > I have incorporated the review changes. > > >> > > > >> > I have also refactored the CacheEventSerializer class and moved > > it > > >> to > > >> > test folder because it is used only in the > > >> > FlinkIgniteSourceSelfExample and > > >> > not required for IgniteSource. > > >> > > > >> > Build links > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821778; > > >> > > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821774; > > >> > > > >> > Please review and share feedback. > > >> > > > >> > Regards > > >> > Saikat > > >> > > > >> > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > >> > saikat.mai...@gmail.com> > > >> > wrote: > > >> > > > >> > > Hi Alexey, > > >> > > > > >> > > Thank you for reviewing the changes and sharing feedback, I am > > >> > > updating the PR. I will share the changes shortly. > > >> > > > > >> > > Regards, > > >> > > Saikat > > >> > > > > >> > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > > >> > > alexey.goncha...@gmail.com> wrote: > > >> > > > > >> > >> Hello Saikat, > > >> > >> > > >> > >> I see a few fellow Igniters added some comments to your PR > > >> > (including > > >> > >> me). > > >> > >> I believe the PR can be merged after you address them. > > >> > >> > > >> > >> Thanks, > > >> > >> AG > > >> > >> > > >> > >> пт, 31 авг. 2018 г. в 3:11, Saikat Maitra < > > >> saikat.mai...@gmail.com > > >> > >: > > >> > >> > > >> > >> > Thank you, Denis > > >> > >> > > > >> > >> > Regards, > > >> > >> > Saikat > > >> > >> > > > >> > >> > On Thu, Aug 30, 2018 at 7:01 PM, Denis Magda < > > >> dma...@apache.org> > > >> > >> wrote: > > >> > >> > > > >> > >> > > Hello Saikat, > > >> > >> > > > > >> > >> > > Hopefully, someone from the community will review the > > >> changes in > > >> > >> the > > >> > >> > > nearest time. > >
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
I agree, which why I initially asked about code freeze (actually it was scope freeze, I apologize). So I prefer to create a new suite and give us some time to run these new tests in master. пн, 1 окт. 2018 г. в 19:34, Nikolay Izhikov : > Alex, Saikat. > > As I can see there is work to be done to merge this feature. > So I think it's better to exclude it from 2.7. > > Thoughts? > > В Пн, 01/10/2018 в 18:35 +0300, Alexey Goncharuk пишет: > > Hello Saikat, > > > > I am ok with the prod code changes, but I am a bit confused with the > > example being added to the tests folder. I think it should be either > added > > to the examples (not sure about the dependency though), or should not be > > added at all. Also, I see that you added a new suite, has it been added > to > > a TC configuration? > > > > > > > > пн, 1 окт. 2018 г. в 16:36, Nikolay Izhikov : > > > > > Hello, Saikat. > > > > > > I have no objections to include this integration to 2.7 release. > > > But, we should ask for a final review from Alex Goncharyuk. > > > > > > Alex, can you comment on this? > > > Is this patch ready to be merged? > > > Do you see any risks to include it to 2.7 release? > > > > > > > > > В Вс, 30/09/2018 в 19:57 -0500, Saikat Maitra пишет: > > > > Hi Alex, Nicolay > > > > > > > > As discussed with Andrew the changes looks good. Would it be ok to > merge > > > > this change to master considering the 2.7 release plan? > > > > > > > > Regards, > > > > Saikat > > > > > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra < > saikat.mai...@gmail.com> > > > > wrote: > > > > > > > > > Thank you Andrew > > > > > > > > > > Regards, > > > > > Saikat > > > > > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > > > andrey.mashen...@gmail.com> wrote: > > > > > > > > > > > Hi Saikat, > > > > > > > > > > > > Sorry for late answer. I've checked changes a day ago. Now, looks > > > > > > good. > > > > > > Hope, it will be merged soon. > > > > > > > > > > > > Alex, would you please merge PR to master. > > > > > > > > > > > > сб, 29 сент. 2018 г., 2:29 Saikat Maitra < > saikat.mai...@gmail.com>: > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > Regards > > > > > > > Saikat > > > > > > > > > > > > > > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > > > > > > saikat.mai...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi Andrew > > > > > > > > > > > > > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > > > > > > > > > > saikat.mai...@gmail.com > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi Andrew, Alexey > > > > > > > > > > > > > > > > > > > > > > I have incorporated the review changes. > > > > > > > > > > > > > > > > > > > > > > I have also refactored the CacheEventSerializer class > and > > > > > > moved it > > > > > > > > > > > > to > > > > > > > > > > > test folder because it is used only in the > > > > > > > > > > > > > > FlinkIgniteSourceSelfExample and > > > > > > > > > > > not required for IgniteSource. > > > > > > > > > > > > > > > > > > > > > > Build links > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;;; > > > > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821774;; > > > > > > ; > > > > > > > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > > > > wrote: > >
[GitHub] ignite pull request #4577: IGNITE-8251 Reduce testPageEviction run time
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4577 ---
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Alex, Saikat. As I can see there is work to be done to merge this feature. So I think it's better to exclude it from 2.7. Thoughts? В Пн, 01/10/2018 в 18:35 +0300, Alexey Goncharuk пишет: > Hello Saikat, > > I am ok with the prod code changes, but I am a bit confused with the > example being added to the tests folder. I think it should be either added > to the examples (not sure about the dependency though), or should not be > added at all. Also, I see that you added a new suite, has it been added to > a TC configuration? > > > > пн, 1 окт. 2018 г. в 16:36, Nikolay Izhikov : > > > Hello, Saikat. > > > > I have no objections to include this integration to 2.7 release. > > But, we should ask for a final review from Alex Goncharyuk. > > > > Alex, can you comment on this? > > Is this patch ready to be merged? > > Do you see any risks to include it to 2.7 release? > > > > > > В Вс, 30/09/2018 в 19:57 -0500, Saikat Maitra пишет: > > > Hi Alex, Nicolay > > > > > > As discussed with Andrew the changes looks good. Would it be ok to merge > > > this change to master considering the 2.7 release plan? > > > > > > Regards, > > > Saikat > > > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > > > wrote: > > > > > > > Thank you Andrew > > > > > > > > Regards, > > > > Saikat > > > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > > andrey.mashen...@gmail.com> wrote: > > > > > > > > > Hi Saikat, > > > > > > > > > > Sorry for late answer. I've checked changes a day ago. Now, looks > > > > good. > > > > > Hope, it will be merged soon. > > > > > > > > > > Alex, would you please merge PR to master. > > > > > > > > > > сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > Regards > > > > > > Saikat > > > > > > > > > > > > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > > > > saikat.mai...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hi Andrew > > > > > > > > > > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > > > > > > > > saikat.mai...@gmail.com > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi Andrew, Alexey > > > > > > > > > > > > > > > > > > > > I have incorporated the review changes. > > > > > > > > > > > > > > > > > > > > I have also refactored the CacheEventSerializer class and > > > > moved it > > > > > > > > > > to > > > > > > > > > > test folder because it is used only in the > > > > > > > > > > > > FlinkIgniteSourceSelfExample and > > > > > > > > > > not required for IgniteSource. > > > > > > > > > > > > > > > > > > > > Build links > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;;; > > > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821774;; > > > > ; > > > > > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > Hi Alexey, > > > > > > > > > > > > > > > > > > > > > > Thank you for reviewing the changes and sharing > > > > feedback, I am > > > > > > > > > > > updating the PR. I will share the changes shortly. > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > > > > > > > > > > > alexey.goncha...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello Saikat, > > > > > >
[jira] [Created] (IGNITE-9756) [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master (timeout).
Pavel Pereslegin created IGNITE-9756: Summary: [Test Failed] IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master (timeout). Key: IGNITE-9756 URL: https://issues.apache.org/jira/browse/IGNITE-9756 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Pavel Pereslegin Assignee: Pavel Pereslegin IgniteCacheIncrementTxTest.testIncrementTxTopologyChange2 fails sometimes in master with timeout. Example of such failure: https://ci.ignite.apache.org/viewLog.html?buildId=1977579=buildResultsDiv=IgniteTests24Java8_Cache2#testNameId-613377372188362920 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4882: IGNITE-9754 Increase timeout waiting for commitLa...
GitHub user oignatenko opened a pull request: https://github.com/apache/ignite/pull/4882 IGNITE-9754 Increase timeout waiting for commitLatch in testRollbackOnTopologyLockPessimistic You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9754 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4882.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4882 commit 1eeca908a8076a8317947dac8a46845964d1d7ea Author: Oleg Ignatenko Date: 2018-08-23T13:13:28Z IGNITE-9348 ML examples improvements - wip (logging improved) -- verified with diffs overview, executing the examples and studying execution logs commit e50b89c392568ba9b93935c4fa6c7f7f93f5ec6f Author: Oleg Ignatenko Date: 2018-08-23T14:45:57Z Revert "IGNITE-9348 ML examples improvements" This reverts commit 1eeca908a8076a8317947dac8a46845964d1d7ea. commit 474024b4c5bbdb3c0a4ed2f0a66238c8054c6674 Author: Oleg Ignatenko Date: 2018-08-23T14:57:34Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 9642b233b5701bdad47ebea163079160227c582a Author: Oleg Ignatenko Date: 2018-08-28T14:01:11Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 7fc16d013ab725d2ff2e1a1b042c983f11d0c4d4 Author: Oleg Ignatenko Date: 2018-08-28T15:13:02Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit d2caba67b156674f051f50faebeafe0871bf0914 Author: Oleg Ignatenko Date: 2018-08-29T13:14:07Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 16775dff51d71ea68b4a3dea98be552130c493ed Author: Oleg Ignatenko Date: 2018-08-30T09:00:56Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit aedb59929974fe205b949225c1a338c68c60cfc8 Author: Oleg Ignatenko Date: 2018-08-30T09:42:38Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 39c6482fcdca506aa33011ed21c98060b4a8c68b Author: Oleg Ignatenko Date: 2018-08-30T11:28:05Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 33b32a2760a6559c78283b927e3191180d8ed9e1 Author: Oleg Ignatenko Date: 2018-08-30T12:31:16Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 9531028ddd1aef9e95f7e8c8b528086739bbb1b0 Author: Oleg Ignatenko Date: 2018-08-30T14:06:34Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 28f22c6e2fffcb82717ba5da7be2cfd39715c4e3 Author: Oleg Ignatenko Date: 2018-08-30T16:41:51Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit aacac88db519187413b0fc5ff9d0e55b8f8cff22 Author: Oleg Ignatenko Date: 2018-08-31T10:12:32Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 897f920dde46022849b13f9fb86dba8e54119a56 Author: Oleg Ignatenko Date: 2018-08-31T13:57:14Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 114c79e54c1b316006ccc3ff22d20d902f9313df Author: Oleg Ignatenko Date: 2018-08-31T17:39:16Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit fd6b659bb8be1992618ce4ce91f568a0988b3afa Author: Oleg Ignatenko Date: 2018-09-02T06:11:42Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 6ae6d1d3cf9743d8d466be0330511ddc8589e944 Author: Oleg Ignatenko Date: 2018-09-03T10:27:35Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit e8b27dbd3d0c1cbdb7a7659175f5c7bb447482bf Author: Oleg Ignatenko Date: 2018-09-04T09:49:44Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 622c82efdd0aa182fadea6b7ffa5d4615521a3f5 Author: Oleg Ignatenko Date: 2018-09-05T10:50:28Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit fb844fe3751e2e8ae87e6b8030b0e4bd659df9c2 Author: Oleg Ignatenko Date: 2018-09-05T11:45:58Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 480ed78869277d7e32f725ab71bec9621f1ac03a Author: Oleg Ignatenko Date: 2018-09-06T07:52:55Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit c99762498f617c0e98ea3062a43c0b30092166ef Author: Oleg Ignatenko Date: 2018-09-06T14:45:04Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 2e17175225c72f747d370b5fee96f8be69d6d2cb Author: Oleg Ignatenko Date: 2018-09-06T17:33:54Z Merge branch 'master' of https://github.com/apache/ignite into master-ml commit 9ebcd9a2fe5966b0bf42a95484395867c15d863f Author: Oleg Ignatenko Date: 2018-09-07T13:38:51Z Merge
[jira] [Created] (IGNITE-9755) PutAllSyncFailover test fail
Alexey Stelmak created IGNITE-9755: -- Summary: PutAllSyncFailover test fail Key: IGNITE-9755 URL: https://issues.apache.org/jira/browse/IGNITE-9755 Project: Ignite Issue Type: Bug Reporter: Alexey Stelmak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9754) Increase timeout waiting for commitLatch in test TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic
Oleg Ignatenko created IGNITE-9754:
--
Summary: Increase timeout waiting for commitLatch in test
TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic
Key: IGNITE-9754
URL: https://issues.apache.org/jira/browse/IGNITE-9754
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Oleg Ignatenko
Current timeout for {{commitLatch}} in test
{{TxRollbackAsyncWithPersistenceTest.testRollbackOnTopologyLockPessimistic}} is
10 seconds.
This looks insufficient to make a compelling reason that test failure indicates
a problem in the implementation. For example log of this [recent failure at
Teamcity|https://ci.ignite.apache.org/viewLog.html?buildId=1970040=buildResultsDiv=IgniteTests24Java8_Cache7]
suggests that there were just a couple of non-critical delays for a few
seconds that made test fail.
Suggest to increase timeout from 10 seconds to 60, so that in case if test
fails waiting on the latch one could assume with reasonable certainty that
something is wrong with the implementation or infrastructure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #4881: IGNITE-9540
GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4881 IGNITE-9540 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9540-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4881.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4881 commit b7d84760eb8dde4b1a922b4ee54885e86644e858 Author: Andrey V. Mashenkov Date: 2018-09-06T07:45:56Z IGNITE-7764: WIP. Tests added. Signed-off-by: Andrey V. Mashenkov commit 98ba5dc4e99e571056f4c0d7061c87f68c0d0aff Author: Andrey V. Mashenkov Date: 2018-09-06T14:28:53Z IGNITE-7764: WIP. Fix Get\GetAll operations. Signed-off-by: Andrey V. Mashenkov commit b88c8b8aa37a493adb64e572e82e7e15c8be88e7 Author: Andrey V. Mashenkov Date: 2018-09-07T19:26:49Z IGNITE-7764: WIP. Fix Put\PutAll operations. Naive implementation, optimization needed. Signed-off-by: Andrey V. Mashenkov commit 09c0a2e8d321da968900af247f41b281cf505599 Author: Andrey V. Mashenkov Date: 2018-09-08T15:01:38Z IGNITE-7764: WIP. Fix test. Signed-off-by: Andrey V. Mashenkov commit 7971694048ab344353808072cbd8826ac958a48d Author: Andrey V. Mashenkov Date: 2018-09-10T10:06:06Z IGNITE-7764: WIP. Refactored query enlist futures. Generify query enlist futures. Signed-off-by: Andrey V. Mashenkov commit a06e80d0a3040e467163359016d5fb2cab8eb8a4 Author: Andrey V. Mashenkov Date: 2018-09-12T14:12:45Z IGNITE-7764: WIP. Implemented MVCC protocol for basic put\putAll\remove\removeAll operations. Signed-off-by: Andrey V. Mashenkov commit 043d42cda73c8d11ec270c8c5739f2d34d58d9fe Author: Andrey V. Mashenkov Date: 2018-09-12T16:33:10Z IGNITE-7764: WIP. Added tests to suite. Signed-off-by: Andrey V. Mashenkov commit 3dffd70991cd782197749575770187705f780c52 Author: Andrey V. Mashenkov Date: 2018-09-13T10:06:06Z IGNITE-7764: WIP. Added tests for remove\removeAll. Signed-off-by: Andrey V. Mashenkov commit bfeed7184bece6b05fac3f2dbcee9e221f50 Author: Andrey V. Mashenkov Date: 2018-09-13T12:20:14Z IGNITE-7764: WIP. Added tests for getAndPut\getAndRemove\putIfAbsent. Added muted test replace/getAndReplace. Signed-off-by: Andrey V. Mashenkov commit 7133ee487ce23a18b60f5fd9980db9a1bf204f25 Author: Andrey V. Mashenkov Date: 2018-09-13T14:07:10Z IGNITE-7764: WIP. Fix tests. Signed-off-by: Andrey V. Mashenkov commit 04925e8795a0db146aa9caf53e3aafadae4dea8c Author: Andrey V. Mashenkov Date: 2018-09-13T15:14:28Z IGNITE-7764: WIP. Mute tests. Signed-off-by: Andrey V. Mashenkov commit f06157575650f5948f5c94a696f546b087d6a455 Author: Andrey V. Mashenkov Date: 2018-09-13T17:52:54Z IGNITE-7764: WIP. Fixed putIfAbsent/replace/getAndReplace. Signed-off-by: Andrey V. Mashenkov commit 8f4bafadeb22e3a420090a674e1c803d3add16c9 Author: Andrey V. Mashenkov Date: 2018-09-14T15:19:39Z IGNITE-7764: WIP. Fixed putIfAbsent/replace/getAndReplace. Signed-off-by: Andrey V. Mashenkov commit 8de70951b5864484fb552087eecf08fa45ace39b Author: Andrey V. Mashenkov Date: 2018-09-14T15:36:00Z IGNITE-7764: WIP. Minor. Signed-off-by: Andrey V. Mashenkov commit bb8f375c9aed9d61a56b75513108e256b9c31a84 Author: Andrey V. Mashenkov Date: 2018-09-14T16:00:10Z IGNITE-7764: WIP. Enable Full API MVCC tests. Signed-off-by: Andrey V. Mashenkov commit a96a6e618bba269ef8c83185a352e5f6df2a1464 Author: Andrey V. Mashenkov Date: 2018-09-14T16:18:50Z IGNITE-7764: WIP. Minors & Styles. Signed-off-by: Andrey V. Mashenkov commit 7e5ca350360b56696f4238c97b5b8b7ee41d976f Author: Andrey V. Mashenkov Date: 2018-09-14T17:41:03Z IGNITE-7764: WIP. Minors. Signed-off-by: Andrey V. Mashenkov commit f65324b1c69458128b5f5a2a0917bc1fe49e2cc1 Author: Andrey V. Mashenkov Date: 2018-09-14T17:53:12Z IGNITE-7764: WIP. Minors after rebase. Signed-off-by: Andrey V. Mashenkov commit 83116012412a4f24de8df2b64d953385060e8724 Author: Andrey V. Mashenkov Date: 2018-09-17T09:25:37Z IGNITE-7764: WIP. Minors. Signed-off-by: Andrey V. Mashenkov commit 0bd02e8939010891854b856c8d77f7f49f13d651 Author: Andrey V. Mashenkov Date: 2018-09-17T10:10:17Z IGNITE-7764: WIP. Minors. Signed-off-by: Andrey V. Mashenkov commit aafbe9c1a9d33086ff78c062f1a06381126e123d Author: Andrey V. Mashenkov Date: 2018-09-17T10:49:22Z IGNITE-7764: WIP. Fix non-versioned read. Signed-off-by: Andrey V. Mashenkov commit 7cb3c54dfac32ba4eea5cb3e03e3daa5b4b7d9bf Author: Andrey V. Mashenkov Date: 2018-09-17T14:42:07Z IGNITE-7764: WIP.
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Hello Saikat, I am ok with the prod code changes, but I am a bit confused with the example being added to the tests folder. I think it should be either added to the examples (not sure about the dependency though), or should not be added at all. Also, I see that you added a new suite, has it been added to a TC configuration? пн, 1 окт. 2018 г. в 16:36, Nikolay Izhikov : > Hello, Saikat. > > I have no objections to include this integration to 2.7 release. > But, we should ask for a final review from Alex Goncharyuk. > > Alex, can you comment on this? > Is this patch ready to be merged? > Do you see any risks to include it to 2.7 release? > > > В Вс, 30/09/2018 в 19:57 -0500, Saikat Maitra пишет: > > Hi Alex, Nicolay > > > > As discussed with Andrew the changes looks good. Would it be ok to merge > > this change to master considering the 2.7 release plan? > > > > Regards, > > Saikat > > > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > > wrote: > > > > > Thank you Andrew > > > > > > Regards, > > > Saikat > > > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > > andrey.mashen...@gmail.com> wrote: > > > > > > > Hi Saikat, > > > > > > > > Sorry for late answer. I've checked changes a day ago. Now, looks > good. > > > > Hope, it will be merged soon. > > > > > > > > Alex, would you please merge PR to master. > > > > > > > > сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > > > > > > > > > Hi Andrew, > > > > > > > > > > I have updated the changes. > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > Regards > > > > > Saikat > > > > > > > > > > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > saikat.mai...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi Andrew > > > > > > > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > Regards > > > > > > Saikat > > > > > > > > > > > > > > > > > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > > > > > > saikat.mai...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > Regards > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > > > > > > saikat.mai...@gmail.com > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Andrew, Alexey > > > > > > > > > > > > > > > > > > I have incorporated the review changes. > > > > > > > > > > > > > > > > > > I have also refactored the CacheEventSerializer class and > moved it > > > > > > > > to > > > > > > > > > test folder because it is used only in the > > > > > > > > > > FlinkIgniteSourceSelfExample and > > > > > > > > > not required for IgniteSource. > > > > > > > > > > > > > > > > > > Build links > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;; > > > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821774; > ; > > > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi Alexey, > > > > > > > > > > > > > > > > > > > > Thank you for reviewing the changes and sharing > feedback, I am > > > > > > > > > > updating the PR. I will share the changes shortly. > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > > > > > > > > > > alexey.goncha...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > Hello Saikat, > > > > > > > > > > > > > > > > > > > > > > I see a few fellow Igniters added some comments to > your PR > > > > > > > > > > (including > > > > > > > > > > > me). > > > > > > > > > > > I believe the PR can be merged after you address them. > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > AG > > > > > > > > > > > > > > > > > > > > > > пт, 31 авг. 2018 г. в 3:11, Saikat Maitra < > > > > > > > > saikat.mai...@gmail.com > > > > > > : > > > > > > > > > > > > > > > > > > > > > > > Thank you, Denis > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > Saikat > >
Re: Apache Ignite 2.7 release
Hello, Igniters. I announce scope freeze for an Apache Ignite 2.7 release. It means: 1. We add to 2.7 only critical bugs. 2. We merge to 2.7 branch only previously announces features. 3. I expect we should exclude or *MERGE ALL TASKS FOR 2.7 DUE TO OCTOBER 10*. So the *October 10 is DEADLINE* for new features. Thoughts? For now we have 34 In Progress tickets planned to 2.7 version [1]. So is you assigned to any of this ticker friendly reminder #1, *the deadline is near :)*. [1] https://issues.apache.org/jira/browse/IGNITE-8803?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.7%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20and%20component%20!%3D%20documentation%20)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20 В Пн, 01/10/2018 в 16:13 +0300, Andrey Gura пишет: > Agree with Andrey. > > IGNITE-9723 will be merged to ignite-2.7 branch soon. > On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov wrote: > > > > Igniters, > > > > There is an inaccuracy in critical worker termination detection, and I'm > > working on a fix right now, see [1]. Also, we have trivial yet important > > fix [2], this one is ready to merge. > > > > I deem both should get to 2.7. Any objections? > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov : > > > > > Folks, > > > > > > We can consider this thread as an almost healthy discussion about SG > > > inclusion to 2.7. > > > > > > For the future, I encourage all Igniters to discuss things before > > > agreement > > > on dev.list instead of trying to log 'some pre-build agreements' here. BTW > > > such logged 'agreements' are not always valid. > > > > > > Dev list is not a log of community actions; it is the principal place > > > where > > > discussion runs. I sincerely hope all similar decisions will be building > > > on > > > the dev list. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov : > > > > > > > Hello, guys. > > > > > > > > I moved SG tasks to 2.8. > > > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > > I fully support Dmitry's concerns. I do not see a single chance for > > > > > > > > Service > > > > > Grid to be included into 2.7 scope, but we are still keeping hope > > > > > > alive. > > > > > What for? Our experience shows, that any feature involving consensus > > > > > algorithms typically take weeks to be finalized after initial public > > > > > review. Yes, it is possible that at some day in October we will see it > > > > > completed, but what about testing? What about regressions with other > > > > > components? Let me reming you that from Monday a lot of efforts will > > > > > be > > > > > > > > put > > > > > into project stabilization. This is the sole purpose of that > > > > > > pre-release > > > > > phase. Accepting a patch with deep rework of Ignite internals in the > > > > > > > > middle > > > > > of that process, means that our effrots will be lost. This is simply a > > > > > matter of respect to contributor's time. > > > > > > > > > > Another problem is that this false hope puts us at rush. Rush during > > > > > design, development, review, testing. Result is known - bad features, > > > > > > > > which > > > > > makes damage to the project. > > > > > > > > > > So my question is - why don't we just want to move it to AI 2.8 right > > > > > > > > now? > > > > > Feature is big, feature is very far from being ready. This simple > > > > > > action > > > > > immediately shifts the focus from dates to quality of the product, and > > > > > remove any risks that potential merge will defeat stabilization > > > > > effrots > > > > > > > > of > > > > > other contributors. > > > > > > > > > > > > > > > > > > > > On Sat, Sep 29, 2018 at 8:32 AM Vyacheslav Daradur < > > > > > > daradu...@gmail.com> > > > > > wrote: > > > > > > > > > > > Dmitriy, > > > > > > > > > > > > Hot redeployment and versioning will not be implemented in phase 1, > > > > > > but it is scheduled once it is finished. > > > > > > > > > > > > Here is an umbrella ticket [1] to track phase 1 scope. > > > > > > > > > > > > It includes very few new features, but we completely rework > > > > > > component > > > > > > to improve guarantees to be more reliable and we build the base for > > > > > > new features. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9607 > > > > > > On Fri, Sep 28, 2018 at 9:38 PM Dmitriy Setrakyan < > > > > > > > > dsetrak...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > > I am not sure I can agree. SG redesign includes: > > > > > > > - hot redeployment > > > > > > > - versioning > > > > > > > > > > > > > > In my experience, features like these take about 1 month to test > > > > > > > > properly > > > > > > > and fix all the
[GitHub] zzzadruga opened a new pull request #23: IGNITE-9541 Add row highlight for 'failed', add title for columns, re…
zzzadruga opened a new pull request #23: IGNITE-9541 Add row highlight for 'failed', add title for columns, re… URL: https://github.com/apache/ignite-teamcity-bot/pull/23 …place JS code with JQuery This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] ignite pull request #4878: IGNITE-9741 SegmentAware recreated every activati...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4878 ---
[jira] [Created] (IGNITE-9753) Control.sh validate index work long and with errors
ARomantsov created IGNITE-9753: -- Summary: Control.sh validate index work long and with errors Key: IGNITE-9753 URL: https://issues.apache.org/jira/browse/IGNITE-9753 Project: Ignite Issue Type: Bug Components: general Affects Versions: 2.5 Reporter: ARomantsov Fix For: 2.8 Errors - [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_1, idxName=_key_PK_hash], class java.lang.NullPointerException: null [12:19:54][:666] IndexValidationIssue [key=null, cacheName=cache_name_2, idxName=_key_PK_hash], class java.lang.NullPointerException: null -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9752) Fix ODBC documentation
Dmitry Sherstobitov created IGNITE-9752: --- Summary: Fix ODBC documentation Key: IGNITE-9752 URL: https://issues.apache.org/jira/browse/IGNITE-9752 Project: Ignite Issue Type: Bug Reporter: Dmitry Sherstobitov Attachments: image-2018-10-01-17-12-21-555.png See screen shot. There is no matching between default values and values in example !image-2018-10-01-17-12-28-557.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Hello, Saikat. I have no objections to include this integration to 2.7 release. But, we should ask for a final review from Alex Goncharyuk. Alex, can you comment on this? Is this patch ready to be merged? Do you see any risks to include it to 2.7 release? В Вс, 30/09/2018 в 19:57 -0500, Saikat Maitra пишет: > Hi Alex, Nicolay > > As discussed with Andrew the changes looks good. Would it be ok to merge > this change to master considering the 2.7 release plan? > > Regards, > Saikat > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > wrote: > > > Thank you Andrew > > > > Regards, > > Saikat > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > andrey.mashen...@gmail.com> wrote: > > > > > Hi Saikat, > > > > > > Sorry for late answer. I've checked changes a day ago. Now, looks good. > > > Hope, it will be merged soon. > > > > > > Alex, would you please merge PR to master. > > > > > > сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > > > > > > > Hi Andrew, > > > > > > > > I have updated the changes. > > > > > > > > Can you please review and share feedback. > > > > > > > > Regards > > > > Saikat > > > > > > > > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra > > > > wrote: > > > > > > > > > Hi Andrew > > > > > > > > > > > > > > > I have updated the changes. > > > > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > Regards > > > > > Saikat > > > > > > > > > > > > > > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > > > > > > saikat.mai...@gmail.com> > > > > > wrote: > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > Can you please review and share feedback. > > > > > > > > > > > > > > > > > > Regards > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > > > > > > > > saikat.mai...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > I have updated the tests and also added java docs. > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > Regards > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > > > > > > saikat.mai...@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Hi Andrew, Alexey > > > > > > > > > > > > > > > > I have incorporated the review changes. > > > > > > > > > > > > > > > > I have also refactored the CacheEventSerializer class and moved > > > > > > > > it > > > > > > to > > > > > > > > test folder because it is used only in the > > > > > > > > FlinkIgniteSourceSelfExample and > > > > > > > > not required for IgniteSource. > > > > > > > > > > > > > > > > Build links > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821778;; > > > > > > > > > > > > > > > > https://ci.ignite.apache.org/viewLog.html?buildId=1821774;; > > > > > > > > > > > > > > > > Please review and share feedback. > > > > > > > > > > > > > > > > Regards > > > > > > > > Saikat > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > > > > > > > > saikat.mai...@gmail.com> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Alexey, > > > > > > > > > > > > > > > > > > Thank you for reviewing the changes and sharing feedback, I am > > > > > > > > > updating the PR. I will share the changes shortly. > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > > > > > > > > > alexey.goncha...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > Hello Saikat, > > > > > > > > > > > > > > > > > > > > I see a few fellow Igniters added some comments to your PR > > > > > > > > (including > > > > > > > > > > me). > > > > > > > > > > I believe the PR can be merged after you address them. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > AG > > > > > > > > > > > > > > > > > > > > пт, 31 авг. 2018 г. в 3:11, Saikat Maitra < > > > > > > saikat.mai...@gmail.com > > > > > : > > > > > > > > > > > > > > > > > > > > > Thank you, Denis > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > Saikat > > > > > > > > > > > > > > > > > > > > > > On Thu, Aug 30, 2018 at 7:01 PM, Denis Magda < > > > > > > dma...@apache.org> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello Saikat, > > > > > > > > > > > > > > > > > > > > > > > > Hopefully, someone from the community will review the > > > > > > changes in > > > > > > > > > > the > > > > > > > > > > > > nearest time. > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Denis > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Aug 30, 2018 at 4:37 PM Saikat Maitra < > > > > > > > > > > > > > > > > > > > > saikat.mai...@gmail.com> > > > > >
Re: Apache Ignite 2.7 release
Agree with Andrey. IGNITE-9723 will be merged to ignite-2.7 branch soon. On Mon, Oct 1, 2018 at 3:56 PM Andrey Kuznetsov wrote: > > Igniters, > > There is an inaccuracy in critical worker termination detection, and I'm > working on a fix right now, see [1]. Also, we have trivial yet important > fix [2], this one is ready to merge. > > I deem both should get to 2.7. Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-9744 > [2] https://issues.apache.org/jira/browse/IGNITE-9723 > > пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov : > > > Folks, > > > > We can consider this thread as an almost healthy discussion about SG > > inclusion to 2.7. > > > > For the future, I encourage all Igniters to discuss things before agreement > > on dev.list instead of trying to log 'some pre-build agreements' here. BTW > > such logged 'agreements' are not always valid. > > > > Dev list is not a log of community actions; it is the principal place where > > discussion runs. I sincerely hope all similar decisions will be building on > > the dev list. > > > > Sincerely, > > Dmitriy Pavlov > > > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov : > > > > > Hello, guys. > > > > > > I moved SG tasks to 2.8. > > > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > > I fully support Dmitry's concerns. I do not see a single chance for > > > Service > > > > Grid to be included into 2.7 scope, but we are still keeping hope > > alive. > > > > What for? Our experience shows, that any feature involving consensus > > > > algorithms typically take weeks to be finalized after initial public > > > > review. Yes, it is possible that at some day in October we will see it > > > > completed, but what about testing? What about regressions with other > > > > components? Let me reming you that from Monday a lot of efforts will be > > > put > > > > into project stabilization. This is the sole purpose of that > > pre-release > > > > phase. Accepting a patch with deep rework of Ignite internals in the > > > middle > > > > of that process, means that our effrots will be lost. This is simply a > > > > matter of respect to contributor's time. > > > > > > > > Another problem is that this false hope puts us at rush. Rush during > > > > design, development, review, testing. Result is known - bad features, > > > which > > > > makes damage to the project. > > > > > > > > So my question is - why don't we just want to move it to AI 2.8 right > > > now? > > > > Feature is big, feature is very far from being ready. This simple > > action > > > > immediately shifts the focus from dates to quality of the product, and > > > > remove any risks that potential merge will defeat stabilization effrots > > > of > > > > other contributors. > > > > > > > > > > > > > > > > On Sat, Sep 29, 2018 at 8:32 AM Vyacheslav Daradur < > > daradu...@gmail.com> > > > > wrote: > > > > > > > > > Dmitriy, > > > > > > > > > > Hot redeployment and versioning will not be implemented in phase 1, > > > > > but it is scheduled once it is finished. > > > > > > > > > > Here is an umbrella ticket [1] to track phase 1 scope. > > > > > > > > > > It includes very few new features, but we completely rework component > > > > > to improve guarantees to be more reliable and we build the base for > > > > > new features. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9607 > > > > > On Fri, Sep 28, 2018 at 9:38 PM Dmitriy Setrakyan < > > > dsetrak...@apache.org> > > > > > wrote: > > > > > > > > > > > > I am not sure I can agree. SG redesign includes: > > > > > > - hot redeployment > > > > > > - versioning > > > > > > > > > > > > In my experience, features like these take about 1 month to test > > > properly > > > > > > and fix all the bugs, including redeployment tests and restart > > tests > > > on > > > > > > larger topologies, together with overnight runs. If this type of > > > testing > > > > > > has not been performed, I think it would be unreasonable to expect > > > this > > > > > > feature making it into the release. > > > > > > > > > > > > Can someone comment on the testing? > > > > > > > > > > > > D. > > > > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 10:38 AM Dmitriy Pavlov < > > > dpavlov@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Nikolay, because I think you're a do'er, but not a commenter, > > like > > > me, > > > > > > > > > > for > > > > > > > example, I can trust your opinion. > > > > > > > > > > > > > > I will join review if I have spare cycles. > > > > > > > > > > > > > > пт, 28 сент. 2018 г. в 20:34, Denis Magda : > > > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > Thanks for stepping in and giving more context. In general, I'm > > > > > > > > > > fully for > > > > > > > > your proposal below: > > > > > > > > > > > > > > > > My vote goes to option *a*. > > > > > > > > > I think we should release 2.7 with the bunch of new cool > > > features. > > > > > > > > > *AND* we should plan 2.8 release at the
[GitHub] ignite pull request #4874: IGNITE-9658
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4874 ---
Re: Request for review : IGNITE-3303 Apache Flink Integration - Flink source
Hi Saikat, I don't mind merging to master, but I have concern if it will go to 2.7. In the separate discussion, we agreed on code freeze should happen during last weekend, September, 30. So it is now up to community and release manager to decide if fix should go to the upcoming release. Usually, after the freeze, only bug/test fixes can be merged to release branch. Hi Nikolay, could you please announce that code freeze happened? Sincerely, Dmitriy Pavlov пн, 1 окт. 2018 г. в 3:58, Saikat Maitra : > Hi Alex, Nicolay > > As discussed with Andrew the changes looks good. Would it be ok to merge > this change to master considering the 2.7 release plan? > > Regards, > Saikat > > On Fri, Sep 28, 2018 at 7:15 PM Saikat Maitra > wrote: > > > Thank you Andrew > > > > Regards, > > Saikat > > > > On Fri, Sep 28, 2018 at 7:00 PM Andrey Mashenkov < > > andrey.mashen...@gmail.com> wrote: > > > >> Hi Saikat, > >> > >> Sorry for late answer. I've checked changes a day ago. Now, looks good. > >> Hope, it will be merged soon. > >> > >> Alex, would you please merge PR to master. > >> > >> сб, 29 сент. 2018 г., 2:29 Saikat Maitra : > >> > >> > Hi Andrew, > >> > > >> > I have updated the changes. > >> > > >> > Can you please review and share feedback. > >> > > >> > Regards > >> > Saikat > >> > > >> > On Sat, Sep 22, 2018 at 2:23 PM Saikat Maitra < > saikat.mai...@gmail.com> > >> > wrote: > >> > > >> > > Hi Andrew > >> > > > >> > > > >> > > I have updated the changes. > >> > > > >> > > > >> > > Can you please review and share feedback. > >> > > > >> > > > >> > > Regards > >> > > Saikat > >> > > > >> > > > >> > > On Wed, Sep 19, 2018 at 8:11 PM, Saikat Maitra < > >> saikat.mai...@gmail.com> > >> > > wrote: > >> > > > >> > >> Hi Andrew, > >> > >> > >> > >> I have updated the tests and also added java docs. > >> > >> > >> > >> Can you please review and share feedback. > >> > >> > >> > >> > >> > >> Regards > >> > >> Saikat > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra < > >> > saikat.mai...@gmail.com> > >> > >> wrote: > >> > >> > >> > >>> Hi Andrew, > >> > >>> > >> > >>> I have updated the tests and also added java docs. > >> > >>> > >> > >>> Please review and share feedback. > >> > >>> > >> > >>> Regards > >> > >>> Saikat > >> > >>> > >> > >>> > >> > >>> On Sat, Sep 8, 2018 at 2:09 PM, Saikat Maitra < > >> saikat.mai...@gmail.com > >> > > > >> > >>> wrote: > >> > >>> > >> > Hi Andrew, Alexey > >> > > >> > I have incorporated the review changes. > >> > > >> > I have also refactored the CacheEventSerializer class and moved > it > >> to > >> > test folder because it is used only in the > >> > FlinkIgniteSourceSelfExample and > >> > not required for IgniteSource. > >> > > >> > Build links > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821778; > >> > > >> > https://ci.ignite.apache.org/viewLog.html?buildId=1821774; > >> > > >> > Please review and share feedback. > >> > > >> > Regards > >> > Saikat > >> > > >> > On Tue, Sep 4, 2018 at 9:57 PM, Saikat Maitra < > >> > saikat.mai...@gmail.com> > >> > wrote: > >> > > >> > > Hi Alexey, > >> > > > >> > > Thank you for reviewing the changes and sharing feedback, I am > >> > > updating the PR. I will share the changes shortly. > >> > > > >> > > Regards, > >> > > Saikat > >> > > > >> > > On Tue, Sep 4, 2018 at 10:59 AM, Alexey Goncharuk < > >> > > alexey.goncha...@gmail.com> wrote: > >> > > > >> > >> Hello Saikat, > >> > >> > >> > >> I see a few fellow Igniters added some comments to your PR > >> > (including > >> > >> me). > >> > >> I believe the PR can be merged after you address them. > >> > >> > >> > >> Thanks, > >> > >> AG > >> > >> > >> > >> пт, 31 авг. 2018 г. в 3:11, Saikat Maitra < > >> saikat.mai...@gmail.com > >> > >: > >> > >> > >> > >> > Thank you, Denis > >> > >> > > >> > >> > Regards, > >> > >> > Saikat > >> > >> > > >> > >> > On Thu, Aug 30, 2018 at 7:01 PM, Denis Magda < > >> dma...@apache.org> > >> > >> wrote: > >> > >> > > >> > >> > > Hello Saikat, > >> > >> > > > >> > >> > > Hopefully, someone from the community will review the > >> changes in > >> > >> the > >> > >> > > nearest time. > >> > >> > > > >> > >> > > -- > >> > >> > > Denis > >> > >> > > > >> > >> > > On Thu, Aug 30, 2018 at 4:37 PM Saikat Maitra < > >> > >> saikat.mai...@gmail.com> > >> > >> > > wrote: > >> > >> > > > >> > >> > > > Hello, > >> > >> > > > > >> > >> > > > The changes for IGNITE-3303 for IgniteSource is complete. > >> This > >> > >> will > >> > >> > help > >> > >> > > is > >> > >> > > > streaming data from Ignite cluster and process, filter, > >> > >> transform and > >> > >> > > > publish it back to Ignite using IgniteSink or in
Re: Apache Ignite 2.7 release
Igniters, There is an inaccuracy in critical worker termination detection, and I'm working on a fix right now, see [1]. Also, we have trivial yet important fix [2], this one is ready to merge. I deem both should get to 2.7. Any objections? [1] https://issues.apache.org/jira/browse/IGNITE-9744 [2] https://issues.apache.org/jira/browse/IGNITE-9723 пн, 1 окт. 2018 г. в 13:13, Dmitriy Pavlov : > Folks, > > We can consider this thread as an almost healthy discussion about SG > inclusion to 2.7. > > For the future, I encourage all Igniters to discuss things before agreement > on dev.list instead of trying to log 'some pre-build agreements' here. BTW > such logged 'agreements' are not always valid. > > Dev list is not a log of community actions; it is the principal place where > discussion runs. I sincerely hope all similar decisions will be building on > the dev list. > > Sincerely, > Dmitriy Pavlov > > вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov : > > > Hello, guys. > > > > I moved SG tasks to 2.8. > > > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > > I fully support Dmitry's concerns. I do not see a single chance for > > Service > > > Grid to be included into 2.7 scope, but we are still keeping hope > alive. > > > What for? Our experience shows, that any feature involving consensus > > > algorithms typically take weeks to be finalized after initial public > > > review. Yes, it is possible that at some day in October we will see it > > > completed, but what about testing? What about regressions with other > > > components? Let me reming you that from Monday a lot of efforts will be > > put > > > into project stabilization. This is the sole purpose of that > pre-release > > > phase. Accepting a patch with deep rework of Ignite internals in the > > middle > > > of that process, means that our effrots will be lost. This is simply a > > > matter of respect to contributor's time. > > > > > > Another problem is that this false hope puts us at rush. Rush during > > > design, development, review, testing. Result is known - bad features, > > which > > > makes damage to the project. > > > > > > So my question is - why don't we just want to move it to AI 2.8 right > > now? > > > Feature is big, feature is very far from being ready. This simple > action > > > immediately shifts the focus from dates to quality of the product, and > > > remove any risks that potential merge will defeat stabilization effrots > > of > > > other contributors. > > > > > > > > > > > > On Sat, Sep 29, 2018 at 8:32 AM Vyacheslav Daradur < > daradu...@gmail.com> > > > wrote: > > > > > > > Dmitriy, > > > > > > > > Hot redeployment and versioning will not be implemented in phase 1, > > > > but it is scheduled once it is finished. > > > > > > > > Here is an umbrella ticket [1] to track phase 1 scope. > > > > > > > > It includes very few new features, but we completely rework component > > > > to improve guarantees to be more reliable and we build the base for > > > > new features. > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9607 > > > > On Fri, Sep 28, 2018 at 9:38 PM Dmitriy Setrakyan < > > dsetrak...@apache.org> > > > > wrote: > > > > > > > > > > I am not sure I can agree. SG redesign includes: > > > > > - hot redeployment > > > > > - versioning > > > > > > > > > > In my experience, features like these take about 1 month to test > > properly > > > > > and fix all the bugs, including redeployment tests and restart > tests > > on > > > > > larger topologies, together with overnight runs. If this type of > > testing > > > > > has not been performed, I think it would be unreasonable to expect > > this > > > > > feature making it into the release. > > > > > > > > > > Can someone comment on the testing? > > > > > > > > > > D. > > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 10:38 AM Dmitriy Pavlov < > > dpavlov@gmail.com> > > > > > wrote: > > > > > > > > > > > Nikolay, because I think you're a do'er, but not a commenter, > like > > me, > > > > > > > > for > > > > > > example, I can trust your opinion. > > > > > > > > > > > > I will join review if I have spare cycles. > > > > > > > > > > > > пт, 28 сент. 2018 г. в 20:34, Denis Magda : > > > > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > Thanks for stepping in and giving more context. In general, I'm > > > > > > > > fully for > > > > > > > your proposal below: > > > > > > > > > > > > > > My vote goes to option *a*. > > > > > > > > I think we should release 2.7 with the bunch of new cool > > features. > > > > > > > > *AND* we should plan 2.8 release at the end of the year with > SG > > > > > > > > > > > > redesign > > > > > > > > and MVCC stabilization tasks. > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Denis > > > > > > > > > > > > > > On Fri, Sep 28, 2018 at 10:30 AM Nikolay Izhikov < > > > > > > > > nizhi...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > > > I think we
[jira] [Created] (IGNITE-9751) Fix odic driver description
Dmitry Sherstobitov created IGNITE-9751: --- Summary: Fix odic driver description Key: IGNITE-9751 URL: https://issues.apache.org/jira/browse/IGNITE-9751 Project: Ignite Issue Type: Bug Affects Versions: 2.7 Reporter: Dmitry Sherstobitov Attachments: Screen Shot 2018-10-01 at 14.55.21.png There is no version and company -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4880: IGNITE-9126 Update Apache Kafka dependency
GitHub user Max-Pudov opened a pull request: https://github.com/apache/ignite/pull/4880 IGNITE-9126 Update Apache Kafka dependency You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9126 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4880.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4880 commit 36cd3c8cff74a27f336d02ee156fa4546746498b Author: Max-Pudov Date: 2018-10-01T10:15:11Z IGNITE-9126 Update Apache Kafka dependency ---
Re: Apache Ignite 2.7 release
Folks, We can consider this thread as an almost healthy discussion about SG inclusion to 2.7. For the future, I encourage all Igniters to discuss things before agreement on dev.list instead of trying to log 'some pre-build agreements' here. BTW such logged 'agreements' are not always valid. Dev list is not a log of community actions; it is the principal place where discussion runs. I sincerely hope all similar decisions will be building on the dev list. Sincerely, Dmitriy Pavlov вс, 30 сент. 2018 г. в 10:49, Nikolay Izhikov : > Hello, guys. > > I moved SG tasks to 2.8. > > В Сб, 29/09/2018 в 17:11 +0300, Vladimir Ozerov пишет: > > I fully support Dmitry's concerns. I do not see a single chance for > Service > > Grid to be included into 2.7 scope, but we are still keeping hope alive. > > What for? Our experience shows, that any feature involving consensus > > algorithms typically take weeks to be finalized after initial public > > review. Yes, it is possible that at some day in October we will see it > > completed, but what about testing? What about regressions with other > > components? Let me reming you that from Monday a lot of efforts will be > put > > into project stabilization. This is the sole purpose of that pre-release > > phase. Accepting a patch with deep rework of Ignite internals in the > middle > > of that process, means that our effrots will be lost. This is simply a > > matter of respect to contributor's time. > > > > Another problem is that this false hope puts us at rush. Rush during > > design, development, review, testing. Result is known - bad features, > which > > makes damage to the project. > > > > So my question is - why don't we just want to move it to AI 2.8 right > now? > > Feature is big, feature is very far from being ready. This simple action > > immediately shifts the focus from dates to quality of the product, and > > remove any risks that potential merge will defeat stabilization effrots > of > > other contributors. > > > > > > > > On Sat, Sep 29, 2018 at 8:32 AM Vyacheslav Daradur > > wrote: > > > > > Dmitriy, > > > > > > Hot redeployment and versioning will not be implemented in phase 1, > > > but it is scheduled once it is finished. > > > > > > Here is an umbrella ticket [1] to track phase 1 scope. > > > > > > It includes very few new features, but we completely rework component > > > to improve guarantees to be more reliable and we build the base for > > > new features. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-9607 > > > On Fri, Sep 28, 2018 at 9:38 PM Dmitriy Setrakyan < > dsetrak...@apache.org> > > > wrote: > > > > > > > > I am not sure I can agree. SG redesign includes: > > > > - hot redeployment > > > > - versioning > > > > > > > > In my experience, features like these take about 1 month to test > properly > > > > and fix all the bugs, including redeployment tests and restart tests > on > > > > larger topologies, together with overnight runs. If this type of > testing > > > > has not been performed, I think it would be unreasonable to expect > this > > > > feature making it into the release. > > > > > > > > Can someone comment on the testing? > > > > > > > > D. > > > > > > > > > > > > On Fri, Sep 28, 2018 at 10:38 AM Dmitriy Pavlov < > dpavlov@gmail.com> > > > > wrote: > > > > > > > > > Nikolay, because I think you're a do'er, but not a commenter, like > me, > > > > > > for > > > > > example, I can trust your opinion. > > > > > > > > > > I will join review if I have spare cycles. > > > > > > > > > > пт, 28 сент. 2018 г. в 20:34, Denis Magda : > > > > > > > > > > > Nikolay, > > > > > > > > > > > > Thanks for stepping in and giving more context. In general, I'm > > > > > > fully for > > > > > > your proposal below: > > > > > > > > > > > > My vote goes to option *a*. > > > > > > > I think we should release 2.7 with the bunch of new cool > features. > > > > > > > *AND* we should plan 2.8 release at the end of the year with SG > > > > > > > > > > redesign > > > > > > > and MVCC stabilization tasks. > > > > > > > > > > > > > > > > > > -- > > > > > > Denis > > > > > > > > > > > > On Fri, Sep 28, 2018 at 10:30 AM Nikolay Izhikov < > > > > > > nizhi...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hello, Igniters. > > > > > > > > > > > > > > I think we shouldn't put so many emotions in discussion of any > > > > > > > contribution. > > > > > > > Even so big and important as SG redesign. > > > > > > > > > > > > > > The crucial point we all agreed about: Service Grid redesign a > big > > > > > > > > > > > > feature > > > > > > > that can significally improve Ignite. > > > > > > > We all want to have it in the product. > > > > > > > > > > > > > > Let me write my vision of the current task state: > > > > > > > > > > > > > > 1. Design of SG is discussed *and aligned* both: privately with > > > > > > Ignite > > > > > > > experts(Vladimir Ozerov, Alexey Goncharyuk, Anton Vinogradov, > Denis > > > > > > > Mekhanikov) > > > > > > > and
[GitHub] ignite pull request #4879: ignite-9447: Fixed benchmarks setup freeze.
GitHub user pavel-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/4879 ignite-9447: Fixed benchmarks setup freeze. Now it is safe to call ignite().close() after setUp if multiply yardstick driver hosts are used. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9447 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4879.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4879 commit c5576c843d4cbceaacacd03ed8d4e75082717c11 Author: Pavel Kuznetsov Date: 2018-09-28T15:30:06Z ignite-9447: Fixed benchmarks setup freeze. Now it is safe to call ignite().close() after setUp if multiply yardstick driver hosts are used. ---
[jira] [Created] (IGNITE-9750) Prohibit near cache configuration for MVCC caches
Ivan Pavlukhin created IGNITE-9750: -- Summary: Prohibit near cache configuration for MVCC caches Key: IGNITE-9750 URL: https://issues.apache.org/jira/browse/IGNITE-9750 Project: Ignite Issue Type: Task Components: mvcc Reporter: Ivan Pavlukhin We should throw an exception when near cache is configured for MVCC cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4868: IGNITE-9736 Fixed public API for Discovery SPI li...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4868 ---
[GitHub] ignite pull request #4878: IGNITE-9741 SegmentAware recreated every activati...
GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/4878 IGNITE-9741 SegmentAware recreated every activation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9741 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4878.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4878 commit 3877ea5ec9b9e4e602ccce198c60ecfff07f8904 Author: Anton Kalashnikov Date: 2018-10-01T09:26:01Z IGNITE-9741 SegmentAware recreated every activation ---
[jira] [Created] (IGNITE-9749) Assertion error in JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite hang
Alexey Goncharuk created IGNITE-9749:
Summary: Assertion error in
JdbcThinTransactionsServerAutoCommitComplexSelfTest leading to JDBC MVCC suite
hang
Key: IGNITE-9749
URL: https://issues.apache.org/jira/browse/IGNITE-9749
Project: Ignite
Issue Type: Bug
Reporter: Alexey Goncharuk
The following assertion can be observed in master
{code}
[10:34:12]W: [org.apache.ignite:ignite-clients] [07:34:12] (err)
Failed to notify listener:
o.a.i.i.util.future.GridEmbeddedFuture$2...@4e56da7bjava.lang.AssertionError:
localNode = 14353600-ea43-42ae-bf7c-4b467800, dhtNodes = [TcpDiscoveryNode
[id=04134719-3eb1-4969-99dc-f520f982, addrs=ArrayList [127.0.0.1],
sockAddrs=HashSet [/127.0.0.1:47501], discPort=47501, order=3, intOrder=3,
lastExchangeTime=1538379249752, loc=false, ver=2.7.0#20181001-sha1:9ab8ebd7,
isClient=false]]
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.backupNodes(GridDhtTxAbstractEnlistFuture.java:867)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.addToBatch(GridDhtTxAbstractEnlistFuture.java:627)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.processEntry(GridDhtTxAbstractEnlistFuture.java:614)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:501)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:363)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxQueryEnlistFuture.map(GridNearTxQueryEnlistFuture.java:212)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.mapOnTopology(GridNearTxAbstractEnlistFuture.java:332)
[10:34:12] : [Step 4/5] [2018-10-01 07:34:12,762][INFO
][exchange-worker-#2510%thin.JdbcThinTransactionsServerAutoCommitComplexSelfTest2%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=4, minorTopVer=16], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=14353600-ea43-42ae-bf7c-4b467800]
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture.access$000(GridNearTxAbstractEnlistFuture.java:56)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture$2.apply(GridNearTxAbstractEnlistFuture.java:340)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxAbstractEnlistFuture$2.apply(GridNearTxAbstractEnlistFuture.java:335)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:385)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:349)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:337)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:497)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:476)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onDone(GridDhtPartitionsExchangeFuture.java:1947)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.finishExchangeOnCoordinator(GridDhtPartitionsExchangeFuture.java:3168)
[10:34:12]W: [org.apache.ignite:ignite-clients] at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAllReceived(GridDhtPartitionsExchangeFuture.java:2934)
[10:34:12]W: [org.apache.ignite:ignite-clients
[GitHub] ignite pull request #4877: IGNITE-5534 added method to activate cluster
GitHub user oleg-ostanin opened a pull request: https://github.com/apache/ignite/pull/4877 IGNITE-5534 added method to activate cluster You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5534 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4877.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4877 commit 019b4df5c9c7dfc4ea94eb7284c4bc932f33074f Author: oleg-ostanin Date: 2018-10-01T07:31:50Z IGNITE-5534 added method to activate cluster ---
Re: [ML] IGNITE-9282 Naive Bayes task split
Great, I support this idea, will help with review too -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
