[jira] [Created] (IGNITE-5726) Duplicate dependencies in POM

2017-07-10 Thread Pavel Konstantinov (JIRA)
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

Re: Enabling memory and persistence metrics

2017-07-10 Thread Denis Magda
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

Re: Apache Ignite 2.1 scope

2017-07-10 Thread Konstantin Boudnik
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

[GitHub] ignite pull request #2278: Ignite gg 12395

2017-07-10 Thread glukos
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

[GitHub] ignite pull request #2277: Ignite-gg-12449 Failed to start node with persist...

2017-07-10 Thread DmitriyGovorukhin
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

[GitHub] ignite pull request #2276: Ignite 5515

2017-07-10 Thread dspavlov
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

[GitHub] ignite pull request #2275: ignite-5662

2017-07-10 Thread EdShangGG
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

[GitHub] ignite pull request #2274: Ignite 5682

2017-07-10 Thread dspavlov
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

Re: JIRA permissions

2017-07-10 Thread Denis Magda
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

[jira] [Created] (IGNITE-5723) Improve code quality for existing code.

2017-07-10 Thread Yury Babak (JIRA)
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

[jira] [Created] (IGNITE-5725) Adopt TracerTest for TC builds.

2017-07-10 Thread Yury Babak (JIRA)
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

[GitHub] ignite pull request #2273: IGNITE-5538 Double check for PersistenceStore mes...

2017-07-10 Thread Jokser
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

Re: Apache Ignite 2.1 scope

2017-07-10 Thread Dmitriy Setrakyan
Vladimir, sounds like a good plan. On Sun, Jul 9, 2017 at 11:43 PM, Vladimir Ozerov wrote: > 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

[GitHub] ignite pull request #2272: IGNITE-5688 Fix SparseDistributedMatrixTest::test...

2017-07-10 Thread artemmalykh
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

[jira] [Created] (IGNITE-5722) Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy

2017-07-10 Thread Andrey Gura (JIRA)
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

[jira] [Created] (IGNITE-5724) Remove all autoboxing staff from the component.

2017-07-10 Thread Yury Babak (JIRA)
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:

[GitHub] ignite pull request #2269: Ignite 5515

2017-07-10 Thread asfgit
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

[GitHub] ignite pull request #2271: IGNITE-5684 Remove FullMap stale updates check

2017-07-10 Thread Jokser
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

[GitHub] ignite pull request #2270: IGNITE-5505 @AffinityKeyMapped annotation is igno...

2017-07-10 Thread kukushal
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

[GitHub] ignite pull request #2269: Ignite 5515

2017-07-10 Thread dspavlov
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

[GitHub] ignite pull request #2268: ignite-5597 fixed documentation

2017-07-10 Thread Litanontaru
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

[GitHub] ignite pull request #2267: IGNITE-5686

2017-07-10 Thread gvvinblade
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

Re: Enabling memory and persistence metrics

2017-07-10 Thread Pavel Tupitsyn
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

Re: Apache Ignite 2.1 scope

2017-07-10 Thread Vladimir Ozerov
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