[GitHub] ignite pull request: ignite-3073

Github user sboikov closed the pull request at: https://github.com/apache/ignite/pull/687 --- 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

[jira] [Created] (IGNITE-3086) Cache store validation should be done only when write entry is enlisted

Alexey Goncharuk created IGNITE-3086: Summary: Cache store validation should be done only when write entry is enlisted Key: IGNITE-3086 URL: https://issues.apache.org/jira/browse/IGNITE-3086

[GitHub] ignite pull request: Correct cluster misses aggregation

Github user krnlMustard closed the pull request at: https://github.com/apache/ignite/pull/686 --- 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

Re: POJO store usability issues

On Wed, May 4, 2016 at 9:12 AM, Alexey Kuznetsov wrote: > > May be, but sending closures is seems as workaround for me. > This will require from user to write quite a lot of code. > Just call of loadCache(...some descriptors...) will be much more user > friendly. > I

[GitHub] ignite pull request: Cluster metrics should merge remote size and ...

GitHub user krnlMustard opened a pull request: https://github.com/apache/ignite/pull/688 Cluster metrics should merge remote size and key size CacheMetric for a cluster was not aggregating remote getSize() and getKeySize() values. Thus the aggregate CacheMetric would report only

[GitHub] ignite pull request: ignite-3073

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/687 ignite-3073 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3073 Alternatively you can review and apply these

[GitHub] ignite pull request: Correct cluster misses aggregation

GitHub user krnlMustard opened a pull request: https://github.com/apache/ignite/pull/686 Correct cluster misses aggregation When merging metrics from a cluster, node hits instead of node misses were being aggregated into merged misses. Thus for clusters the CacheMetrics were

Re: Spark/YARN

Hi Naden,I am just wondering why you want to start ignite node in Yarn.You can stary the independent ignite node.What benefit you are getting by making part of yarn cluster.I am asking this because i too had the same queries but latet on i switched to starting independent ignite node on the

Re: Ignite 1.6 release timelines

Resending (fixed links) On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan wrote: > Igniters, > > Looks like we are almost done with the outstanding issues, mainly ODBC > support and cache concurrent map changes. As far as the concurrent map, we > had a performance drop,

[GitHub] ignite pull request: Ignite gg 11121

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/685 Ignite gg 11121 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11121 Alternatively you can review and

Re: Ignite 1.6 release timelines

Igniters, Looks like we are almost done with the outstanding issues, mainly ODBC support and cache concurrent map changes. As far as the concurrent map, we had a performance drop, and I think it is pretty important that we address it prior to the release. Can we please get an update for these

[GitHub] ignite pull request: Ignite gg 11121

Github user dkarachentsev closed the pull request at: https://github.com/apache/ignite/pull/682 --- 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

[GitHub] ignite pull request: Ignite 3018

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/684 Ignite 3018 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3018 Alternatively you can review and apply

[GitHub] ignite pull request: ignite-3041

Github user ascherbakoff closed the pull request at: https://github.com/apache/ignite/pull/663 --- 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

[GitHub] ignite pull request: Ignite-2854 Deadlock detection for pessimisti...

Github user agura closed the pull request at: https://github.com/apache/ignite/pull/656 --- 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: ignite-2982

Github user ascherbakoff closed the pull request at: https://github.com/apache/ignite/pull/676 --- 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

[GitHub] ignite pull request: Ignite gg 11121

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/682 Ignite gg 11121 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11121 Alternatively you can review and

Cache errors with enabled indexing

Guys, I've implemented CacheOffheapBatchIndexingTest containing various tests for batch cache operations with enabled indexing. *testBatchRemovetest *fails when H2 row value is the instance of BinaryObjectOffheapImpl. I was able to fix

[GitHub] ignite pull request: ignite-3073

Github user sboikov closed the pull request at: https://github.com/apache/ignite/pull/680 --- 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

[jira] [Created] (IGNITE-3084) Investigate how Ignite can support Spark DataFrame

Vladimir Ozerov created IGNITE-3084: --- Summary: Investigate how Ignite can support Spark DataFrame Key: IGNITE-3084 URL: https://issues.apache.org/jira/browse/IGNITE-3084 Project: Ignite

[jira] [Created] (IGNITE-3083) Shmem loader failed with OverlappingFileLockException

Nikolay Tikhonov created IGNITE-3083: Summary: Shmem loader failed with OverlappingFileLockException Key: IGNITE-3083 URL: https://issues.apache.org/jira/browse/IGNITE-3083 Project: Ignite

[jira] [Created] (IGNITE-3081) NearCacheConfiguration incorrectly extends MutableConfiguration

Pavel Tupitsyn created IGNITE-3081: -- Summary: NearCacheConfiguration incorrectly extends MutableConfiguration Key: IGNITE-3081 URL: https://issues.apache.org/jira/browse/IGNITE-3081 Project: Ignite

[GitHub] ignite pull request: gridgain-7.5.18

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/681 gridgain-7.5.18 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.18 Alternatively you can review and apply

[jira] [Created] (IGNITE-3080) Improve Spark documentation for CDH deployment

Vladimir Ozerov created IGNITE-3080: --- Summary: Improve Spark documentation for CDH deployment Key: IGNITE-3080 URL: https://issues.apache.org/jira/browse/IGNITE-3080 Project: Ignite Issue

Re: 1.5.0.final is breaking packaging: osgi dependency is non-existent

Roman, Raul, As far as I remember you're familiar with OSGI. Could you please have a look at this? On Wed, May 4, 2016 at 6:09 AM, Konstantin Boudnik wrote: > Hey guys > > For your information: adding osgi into the product is breaking the > dependency matrix of the bigtop

[GitHub] ignite pull request: ignite-3073

GitHub user sboikov opened a pull request: https://github.com/apache/ignite/pull/680 ignite-3073 ignite-3073 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3073 Alternatively you can review and