[jira] [Created] (IGNITE-5726) Duplicate dependencies in POM
Pavel Konstantinov created IGNITE-5726: -- Summary: Duplicate dependencies in POM Key: IGNITE-5726 URL: https://issues.apache.org/jira/browse/IGNITE-5726 Project: Ignite Issue Type: Bug Reporter: Pavel Konstantinov Import models from database Look at POM on Summary page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Enabling memory and persistence metrics
Hi Pavel, thanks. However, how do I enable the metrics for the default memory region (policy)? I’m talking about the use case when there are no custom memory regions/policies defined. Is it supposed that the user need to recreate the default policy configuration from sratch just in order to enable the metrics? Can we add “MemoryConfiguration.setMetricsEnabled” method that will enable metrics for all the regions we have? — Denis > On Jul 10, 2017, at 1:44 AM, Pavel Tupitsynwrote: > > Hi Denis, > > See PersistentStoreConfiguration.metricsEnabled, MemoryPolicyConfiguration. > metricsEnabled > > On Sat, Jul 8, 2017 at 2:55 AM, Denis Magda wrote: > >> Sergey, >> >> How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation >> if a have only the default region set and don’t wanna use the JMX beans >> available? >> >> Struggling to find any API method to do that. Hope we didn’t forget to >> support such an obvious thing. >> >> — >> Denis
Re: Apache Ignite 2.1 scope
That's an interesting statement to make, considering the a PMC is legally responsible for the release they are making and voting for. What I believe it would achieve is to give a wider group of our users a chance to get and install the new version and try some of the most prominent features, while giving the feedback. Even if expressed in the form of non-binding votes. -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Sat, Jul 8, 2017 at 8:26 AM, Dmitriy Setrakyanwrote: > Cos, > > I am not sure what a 7 day vote will accomplish. As we all know, Apache > [VOTE] is not about the release quality, but about proper build procedure, > release signing, and licensing. I do not see the community needing more > time than usual to verify this release. > > D. > > On Fri, Jul 7, 2017 at 8:14 PM, Konstantin Boudnik wrote: > >> Fair enough, I will try to collect more and share with the team. >> >> And +1 on the proposed release schedule: considering the complexity of the >> changes we better have some time to play with the bits. In fact, I'd >> suggest >> we give it 7 days for the [VOTE] so people have time to play with the bits. >> Thoughts? >> >> Cos >> >> On Thu, Jul 06, 2017 at 11:06AM, Vladimir Ozerov wrote: >> > Cos, >> > >> > I am not aware of performance degradation in regards to Cassandra. AFAIK >> > there were extensive benchmarking prior to 2.0 release. And in the end >> 2.0 >> > release had performance not worse than 1.9. If you have more information >> on >> > the matter, let's discuss it in the separate thread. >> > >> > On Thu, Jul 6, 2017 at 11:04 AM, Vladimir Ozerov >> > wrote: >> > >> > > Vyacheslav, Denis, >> > > >> > > 7 July is too abrupt date. Scope of 2.1 is still too broad, and what is >> > > more important - persistent store has been merged only several days >> ago. We >> > > need some room for stabilization. I propose the following timeline: >> > > 16 July - code freeze >> > > 17-21 July - QA >> > > 21-24 July - vote and release >> > > >> > > On Thu, Jul 6, 2017 at 4:30 AM, Konstantin Boudnik >> wrote: >> > > >> > >> Thanks everyone for giving us enough time to take a look into the code >> > >> and architecture of this new feature. The webinar was certainly quite >> > >> helpful (thanks Denis!). >> > >> >> > >> It seems to be a good time to add the feature into the dot-release, so >> > >> more users can have a taste of it "officially". I have a somewhat >> > >> unrelated question though: it seems that 2.0 has significant >> > >> performance degradation compared to 1.8 when it get to the working >> > >> with external distributed storage (like Cassandra). Could it be caused >> > >> by all the changes that were made between 1.8 and 2.0 in the >> > >> preparation for the coming persistent store functionality? Are we >> > >> publishing/collecting say yardstick reports for our own releases? >> > >> >> > >> Thanks! >> > >> Cos >> > >> -- >> > >> Take care, >> > >> Konstantin (Cos) Boudnik >> > >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 >> > >> >> > >> Disclaimer: Opinions expressed in this email are those of the author, >> > >> and do not necessarily represent the views of any company the author >> > >> might be affiliated with at the moment of writing. >> > >> >> > >> >> > >> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov > > >> > >> wrote: >> > >> > Igniters, >> > >> > >> > >> > Persistent store has been merged to master branch! "master-bak" >> branch >> > >> was >> > >> > created to keep the state before merge for safety. As release date >> for >> > >> 2.1 >> > >> > is mid July, I created "ignite-2.1" branch where we will stabilize >> the >> > >> > release as usual. Please push features and fixes planned for 2.1 >> > >> release to >> > >> > this branch. The rest commits should go to master. >> > >> > >> > >> > Vladimir. >> > >> > >> > >> > On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov < >> voze...@gridgain.com> >> > >> > wrote: >> > >> > >> > >> >> Hi Denis, >> > >> >> >> > >> >> Awesome news! I'll take care of necessary release procedures if >> nobody >> > >> >> minds. >> > >> >> >> > >> >> Vladimir. >> > >> >> >> > >> >> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda >> > >> wrote: >> > >> >> >> > >> >>> Igniters, >> > >> >>> >> > >> >>> It’s time to refresh this abandoned thread and finally rollout >> out all >> > >> >>> the changes appeared in 2.1. >> > >> >>> >> > >> >>> In addition, recently donated Persistent Store got the green light >> > >> [1] to >> > >> >>> become a part of the master branch (no one asked for extra time to >> > >> dive >> > >> >>> into its details) and, personally, it’s absolutely fine to make it
[GitHub] ignite pull request #2278: Ignite gg 12395
GitHub user glukos opened a pull request: https://github.com/apache/ignite/pull/2278 Ignite gg 12395 PR for tests run. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12395 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2278.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 #2278 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date: 2017-07-07T16:22:59Z IGNITE-5369 Added support
[GitHub] ignite pull request #2277: Ignite-gg-12449 Failed to start node with persist...
GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/2277 Ignite-gg-12449 Failed to start node with persistence store after restart You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12449 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2277.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 #2277 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date:
[GitHub] ignite pull request #2276: Ignite 5515
GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2276 Ignite 5515 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5515 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2276.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 #2276 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date: 2017-07-07T16:22:59Z IGNITE-5369 Added support for _key and _val names
[GitHub] ignite pull request #2275: ignite-5662
GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/2275 ignite-5662 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5662 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2275.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 #2275 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date: 2017-07-07T16:22:59Z IGNITE-5369 Added support for _key and _val names
[GitHub] ignite pull request #2274: Ignite 5682
GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2274 Ignite 5682 Locating failure of GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5682 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2274.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 #2274 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko
Re: JIRA permissions
Hello Evgeniy, Granted you the required permissions. Please go ahead and pick a ticket of interest. Below is auxiliary info that might be useful to you. Get familiar with Ignite development process described here: https://cwiki.apache.org/confluence/display/IGNITE/Development+Process Instructions on how to contribute can be found here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Project setup in Intellij IDEA: https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup Once you got familiar and were able to run a few examples, you should pick a Jira ticket you would like to start on. Send an email to the dev list sharing your JIRA id, so we can add you as a contributor in Jira. These are the easy tickets to start with: https://issues.apache.org/jira/browse/IGNITE-4549?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN While those are more advanced but appealing: https://ignite.apache.org/community/contribute.html#pick-ticket Looking forward to your contributions! — Denis > On Jul 9, 2017, at 11:54 PM, Evgeniy Ignatiev> wrote: > > Hello. > > I am interested in Apache Ignite and would like to contribute to the project. > > Please grant me JIRA permission to assign tickets to myself. My JIRA account > is eignatiev. > > Best regards. > >
[jira] [Created] (IGNITE-5723) Improve code quality for existing code.
Yury Babak created IGNITE-5723: -- Summary: Improve code quality for existing code. Key: IGNITE-5723 URL: https://issues.apache.org/jira/browse/IGNITE-5723 Project: Ignite Issue Type: Improvement Components: ml Environment: (?) check code style for all sources. (?) check code coverage. Reporter: Yury Babak -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5725) Adopt TracerTest for TC builds.
Yury Babak created IGNITE-5725: -- Summary: Adopt TracerTest for TC builds. Key: IGNITE-5725 URL: https://issues.apache.org/jira/browse/IGNITE-5725 Project: Ignite Issue Type: Bug Components: ml Reporter: Yury Babak Currently TracerTest runs browser but we don`t have even X11 on TC. So we need to decide - run add possibility to run browser on TC, change tests and don`t call "Desktop.getDesktop().browse" during TC build or just ignore this test for TC build. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #2273: IGNITE-5538 Double check for PersistenceStore mes...
GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2273 IGNITE-5538 Double check for PersistenceStore message factory existence. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5538 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2273.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 #2273 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date:
Re: Apache Ignite 2.1 scope
Vladimir, sounds like a good plan. On Sun, Jul 9, 2017 at 11:43 PM, Vladimir Ozerovwrote: > Folks, > > I monitored TeamCity state over several days, as well as "In Progress" > tickets. My observation is that situation gradually improving, number of > failing tests goes down, and most of the tickets in work are already > dedicated to stabilization, rather to new development. Provided that > release already has a killer-feature and a number of smaller improvements, > I propose to do the following: > - Freeze the scope right now, no more features, only stabilization > - Dedicate this week to bug fixes > - Pass to vote in the end of the week, say 14 July. > > Without this I am afraid product quality will be at risk, as Persistent > Store is a huge thing, which could interfere with other components in > subtle ways. > > Any objections on the plan? > > Vladimir. > > > On Sat, Jul 8, 2017 at 6:26 PM, Dmitriy Setrakyan > wrote: > > > Cos, > > > > I am not sure what a 7 day vote will accomplish. As we all know, Apache > > [VOTE] is not about the release quality, but about proper build > procedure, > > release signing, and licensing. I do not see the community needing more > > time than usual to verify this release. > > > > D. > > > > On Fri, Jul 7, 2017 at 8:14 PM, Konstantin Boudnik > wrote: > > > > > Fair enough, I will try to collect more and share with the team. > > > > > > And +1 on the proposed release schedule: considering the complexity of > > the > > > changes we better have some time to play with the bits. In fact, I'd > > > suggest > > > we give it 7 days for the [VOTE] so people have time to play with the > > bits. > > > Thoughts? > > > > > > Cos > > > > > > On Thu, Jul 06, 2017 at 11:06AM, Vladimir Ozerov wrote: > > > > Cos, > > > > > > > > I am not aware of performance degradation in regards to Cassandra. > > AFAIK > > > > there were extensive benchmarking prior to 2.0 release. And in the > end > > > 2.0 > > > > release had performance not worse than 1.9. If you have more > > information > > > on > > > > the matter, let's discuss it in the separate thread. > > > > > > > > On Thu, Jul 6, 2017 at 11:04 AM, Vladimir Ozerov < > voze...@gridgain.com > > > > > > > wrote: > > > > > > > > > Vyacheslav, Denis, > > > > > > > > > > 7 July is too abrupt date. Scope of 2.1 is still too broad, and > what > > is > > > > > more important - persistent store has been merged only several days > > > ago. We > > > > > need some room for stabilization. I propose the following timeline: > > > > > 16 July - code freeze > > > > > 17-21 July - QA > > > > > 21-24 July - vote and release > > > > > > > > > > On Thu, Jul 6, 2017 at 4:30 AM, Konstantin Boudnik > > > > wrote: > > > > > > > > > >> Thanks everyone for giving us enough time to take a look into the > > code > > > > >> and architecture of this new feature. The webinar was certainly > > quite > > > > >> helpful (thanks Denis!). > > > > >> > > > > >> It seems to be a good time to add the feature into the > dot-release, > > so > > > > >> more users can have a taste of it "officially". I have a somewhat > > > > >> unrelated question though: it seems that 2.0 has significant > > > > >> performance degradation compared to 1.8 when it get to the working > > > > >> with external distributed storage (like Cassandra). Could it be > > caused > > > > >> by all the changes that were made between 1.8 and 2.0 in the > > > > >> preparation for the coming persistent store functionality? Are we > > > > >> publishing/collecting say yardstick reports for our own releases? > > > > >> > > > > >> Thanks! > > > > >> Cos > > > > >> -- > > > > >> Take care, > > > > >> Konstantin (Cos) Boudnik > > > > >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > > > > >> > > > > >> Disclaimer: Opinions expressed in this email are those of the > > author, > > > > >> and do not necessarily represent the views of any company the > author > > > > >> might be affiliated with at the moment of writing. > > > > >> > > > > >> > > > > >> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov < > > voze...@gridgain.com > > > > > > > > >> wrote: > > > > >> > Igniters, > > > > >> > > > > > >> > Persistent store has been merged to master branch! "master-bak" > > > branch > > > > >> was > > > > >> > created to keep the state before merge for safety. As release > date > > > for > > > > >> 2.1 > > > > >> > is mid July, I created "ignite-2.1" branch where we will > stabilize > > > the > > > > >> > release as usual. Please push features and fixes planned for 2.1 > > > > >> release to > > > > >> > this branch. The rest commits should go to master. > > > > >> > > > > > >> > Vladimir. > > > > >> > > > > > >> > On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov < > > > voze...@gridgain.com> > > > > >> > wrote: > > > > >> > > > > > >> >> Hi Denis, > > > > >> >> > > > > >> >> Awesome news! I'll take care of necessary release procedures if > > >
[GitHub] ignite pull request #2272: IGNITE-5688 Fix SparseDistributedMatrixTest::test...
GitHub user artemmalykh opened a pull request: https://github.com/apache/ignite/pull/2272 IGNITE-5688 Fix SparseDistributedMatrixTest::testCacheBehaviour crash Fixed tests of cache behaviour for sparse distributed matrix. Also code style fixes are done for various ml-module file. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5688 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2272.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 #2272 commit ce323a7550ee2b3e0b242abce0842ebcebb09b83 Author: artemmalykhDate: 2017-07-10T12:50:10Z IGNITE-5688 Fix SparseDistributedMatrixTest::testCacheBehaviour crash --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (IGNITE-5722) Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy
Andrey Gura created IGNITE-5722: --- Summary: Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy Key: IGNITE-5722 URL: https://issues.apache.org/jira/browse/IGNITE-5722 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 1.0 Reporter: Andrey Gura Assignee: Andrey Gura Fix For: 2.1 Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy. In PeekValueExpiryAwareIterator.value() method the entry should be touched after unswap. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5724) Remove all autoboxing staff from the component.
Yury Babak created IGNITE-5724: -- Summary: Remove all autoboxing staff from the component. Key: IGNITE-5724 URL: https://issues.apache.org/jira/browse/IGNITE-5724 Project: Ignite Issue Type: Improvement Components: ml Reporter: Yury Babak Find and remove all boxing/unboxing code from vectors and matrices. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #2269: Ignite 5515
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2269 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request #2271: IGNITE-5684 Remove FullMap stale updates check
GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/2271 IGNITE-5684 Remove FullMap stale updates check You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5684 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2271.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 #2271 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date: 2017-07-07T16:22:59Z IGNITE-5369 Added
[GitHub] ignite pull request #2270: IGNITE-5505 @AffinityKeyMapped annotation is igno...
GitHub user kukushal opened a pull request: https://github.com/apache/ignite/pull/2270 IGNITE-5505 @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-5505 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2270.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 #2270 commit c0a0e1340d3576b9880eaf9c9ad431cde85e5429 Author: Alexey KukushkinDate: 2017-07-07T15:54:39Z test for IGNITE-5505 commit 67e1457d4fd62bbd5004a60a8d3e1799b4125c9a Author: Alexey Kukushkin Date: 2017-07-07T16:49:23Z Fix code style commit 5023ff50fb461d37fb2b05a7c8a01fc6091028ba Author: Alexey Kukushkin Date: 2017-07-10T10:44:49Z Solution for IGNITE-5505 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request #2269: Ignite 5515
GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/2269 Ignite 5515 PR for enable hang up test on TC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5515 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2269.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 #2269 commit ab5267134966b466a2d4bfba15d0c7e3ebe91139 Author: sboikovDate: 2017-07-07T10:14:18Z 2.1 More simple tx cancel on node stop commit 85d8c6572d78c7d6796906d92b566e2fa5b116be Author: Dmitriy Govorukhin Date: 2017-07-07T10:13:55Z IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest commit f589628f4846f14efc8e702b61856cc90a3d0dc7 Author: sboikov Date: 2017-07-07T10:52:38Z Rename ActionData -> CacheActionData. commit 30922ed8ac518749a2559aff51fe183a890041bb Author: Alexey Kuznetsov Date: 2017-07-07T11:03:18Z ignite-2.1 Added map with previous snapshots. commit 99fd75dd7766318af88a38b5640a648bba3ccdf1 Author: Sergey Kalashnikov Date: 2017-07-07T11:38:36Z IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes #2248. commit 4fc8124d9538625cb0a95c918634b43ec1319bee Author: sboikov Date: 2017-07-07T11:43:28Z Fixed formatting. commit 984ab5bd3c08b2af9222964451acc281b92814b8 Author: sboikov Date: 2017-07-07T11:43:50Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71 Author: sboikov Date: 2017-07-07T11:49:13Z Fixed formatting. commit 2a5390b1c083819f059e449b34a5979ec35b7755 Author: Alexander Paschenko Date: 2017-07-07T12:01:43Z IGNITE-5159: DDL example. This closes #2227. commit d232648711c882ed304eae89ae19f151067649fd Author: devozerov Date: 2017-07-07T12:02:29Z Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2 commit a9387adef490086406b05fe961ff0f3151045caa Author: Pavel Tupitsyn Date: 2017-07-07T12:21:20Z IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence tests as a workaround for OOM on default settings commit 13399d530f3458c3bf59634857cb05f801e8cc34 Author: sboikov Date: 2017-07-07T12:24:09Z 2.1 Fixed assert (cacheName can be null here). commit ea4420e6aad509c4ae58d6d0880918c98fd1959a Author: sboikov Date: 2017-07-07T12:24:26Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4 Author: Sergey Kalashnikov Date: 2017-07-07T12:54:52Z IGNITE-5204: Fixed NPE on certain data with index inlining. This closes #2115. commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828 Author: sboikov Date: 2017-07-07T12:55:18Z Removed unused method GridDhtPartitionTopology.checkEvictions(). commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7 Author: sboikov Date: 2017-07-07T12:55:38Z Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2 commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4 Author: Sergey Kalashnikov Date: 2017-07-07T13:30:37Z IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast optimization, when WHERE clause argument type was different from key or affinity key type. This close #2107. commit 3c887378eb64d2d236073410070082e5699e8334 Author: Igor Sapego Date: 2017-07-07T13:52:31Z IGNITE-5582: Implemented Compute::Broadcast for C++ (cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095) commit 3314a4513c816c027dad80258ded1fe5a4c2b700 Author: sboikov Date: 2017-07-07T14:28:47Z Fixed cache plugin validation. commit 517a23d252078e62a8addca55ca78497e5226b5b Author: mcherkasov Date: 2017-06-30T17:23:55Z IGNITE-5554 ServiceProcessor may process failed reassignments in timeout thread commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda Author: Ilya Lantukh Date: 2017-07-07T15:55:27Z IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after rebalancing commit e5c2ec5a62c0d5fc268275ea9277f6933a582966 Author: Alexey Kuznetsov Date: 2017-07-07T16:06:52Z ignite-2.1 Minor. commit eb37f538f55a471258e49ee2fbf0e8f234829def Author: vsisko Date: 2017-07-07T16:22:59Z IGNITE-5369 Added
[GitHub] ignite pull request #2268: ignite-5597 fixed documentation
GitHub user Litanontaru opened a pull request: https://github.com/apache/ignite/pull/2268 ignite-5597 fixed documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/Litanontaru/ignite ignite-5597 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2268.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 #2268 commit bb2dac562e5020f25384ee5d34737736e9ca0958 Author: Andrei_YakushinDate: 2017-07-10T10:07:40Z ignite-5597 fixed documentation --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] ignite pull request #2267: IGNITE-5686
GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/2267 IGNITE-5686 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5686 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2267.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 #2267 commit 0761c41a04ccfc4cee1d055753adca3e60388d94 Author: Igor SeliverstovDate: 2017-07-10T09:44:10Z IGNITE-5686 Endless partition eviction during node shutdown --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Enabling memory and persistence metrics
Hi Denis, See PersistentStoreConfiguration.metricsEnabled, MemoryPolicyConfiguration. metricsEnabled On Sat, Jul 8, 2017 at 2:55 AM, Denis Magdawrote: > Sergey, > > How do I enable MemoryMetrics and PersistenceMetrics metrics aggregation > if a have only the default region set and don’t wanna use the JMX beans > available? > > Struggling to find any API method to do that. Hope we didn’t forget to > support such an obvious thing. > > — > Denis
Re: Apache Ignite 2.1 scope
Folks, I monitored TeamCity state over several days, as well as "In Progress" tickets. My observation is that situation gradually improving, number of failing tests goes down, and most of the tickets in work are already dedicated to stabilization, rather to new development. Provided that release already has a killer-feature and a number of smaller improvements, I propose to do the following: - Freeze the scope right now, no more features, only stabilization - Dedicate this week to bug fixes - Pass to vote in the end of the week, say 14 July. Without this I am afraid product quality will be at risk, as Persistent Store is a huge thing, which could interfere with other components in subtle ways. Any objections on the plan? Vladimir. On Sat, Jul 8, 2017 at 6:26 PM, Dmitriy Setrakyanwrote: > Cos, > > I am not sure what a 7 day vote will accomplish. As we all know, Apache > [VOTE] is not about the release quality, but about proper build procedure, > release signing, and licensing. I do not see the community needing more > time than usual to verify this release. > > D. > > On Fri, Jul 7, 2017 at 8:14 PM, Konstantin Boudnik wrote: > > > Fair enough, I will try to collect more and share with the team. > > > > And +1 on the proposed release schedule: considering the complexity of > the > > changes we better have some time to play with the bits. In fact, I'd > > suggest > > we give it 7 days for the [VOTE] so people have time to play with the > bits. > > Thoughts? > > > > Cos > > > > On Thu, Jul 06, 2017 at 11:06AM, Vladimir Ozerov wrote: > > > Cos, > > > > > > I am not aware of performance degradation in regards to Cassandra. > AFAIK > > > there were extensive benchmarking prior to 2.0 release. And in the end > > 2.0 > > > release had performance not worse than 1.9. If you have more > information > > on > > > the matter, let's discuss it in the separate thread. > > > > > > On Thu, Jul 6, 2017 at 11:04 AM, Vladimir Ozerov > > > > wrote: > > > > > > > Vyacheslav, Denis, > > > > > > > > 7 July is too abrupt date. Scope of 2.1 is still too broad, and what > is > > > > more important - persistent store has been merged only several days > > ago. We > > > > need some room for stabilization. I propose the following timeline: > > > > 16 July - code freeze > > > > 17-21 July - QA > > > > 21-24 July - vote and release > > > > > > > > On Thu, Jul 6, 2017 at 4:30 AM, Konstantin Boudnik > > wrote: > > > > > > > >> Thanks everyone for giving us enough time to take a look into the > code > > > >> and architecture of this new feature. The webinar was certainly > quite > > > >> helpful (thanks Denis!). > > > >> > > > >> It seems to be a good time to add the feature into the dot-release, > so > > > >> more users can have a taste of it "officially". I have a somewhat > > > >> unrelated question though: it seems that 2.0 has significant > > > >> performance degradation compared to 1.8 when it get to the working > > > >> with external distributed storage (like Cassandra). Could it be > caused > > > >> by all the changes that were made between 1.8 and 2.0 in the > > > >> preparation for the coming persistent store functionality? Are we > > > >> publishing/collecting say yardstick reports for our own releases? > > > >> > > > >> Thanks! > > > >> Cos > > > >> -- > > > >> Take care, > > > >> Konstantin (Cos) Boudnik > > > >> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > > > >> > > > >> Disclaimer: Opinions expressed in this email are those of the > author, > > > >> and do not necessarily represent the views of any company the author > > > >> might be affiliated with at the moment of writing. > > > >> > > > >> > > > >> On Tue, Jul 4, 2017 at 3:20 AM, Vladimir Ozerov < > voze...@gridgain.com > > > > > > >> wrote: > > > >> > Igniters, > > > >> > > > > >> > Persistent store has been merged to master branch! "master-bak" > > branch > > > >> was > > > >> > created to keep the state before merge for safety. As release date > > for > > > >> 2.1 > > > >> > is mid July, I created "ignite-2.1" branch where we will stabilize > > the > > > >> > release as usual. Please push features and fixes planned for 2.1 > > > >> release to > > > >> > this branch. The rest commits should go to master. > > > >> > > > > >> > Vladimir. > > > >> > > > > >> > On Mon, Jul 3, 2017 at 4:18 PM, Vladimir Ozerov < > > voze...@gridgain.com> > > > >> > wrote: > > > >> > > > > >> >> Hi Denis, > > > >> >> > > > >> >> Awesome news! I'll take care of necessary release procedures if > > nobody > > > >> >> minds. > > > >> >> > > > >> >> Vladimir. > > > >> >> > > > >> >> On Sat, Jul 1, 2017 at 12:25 AM, Denis Magda > > > >> wrote: > > > >> >> > > > >> >>> Igniters, > > > >> >>> > > > >> >>> It’s time to refresh this abandoned thread and finally rollout > > out all > > > >> >>> the changes appeared in 2.1. > > > >> >>> > > > >> >>> In addition, recently donated