[jira] [Created] (IGNITE-3464) Possible race between partition exchange and prepare/finish requests

Alexey Goncharuk created IGNITE-3464: Summary: Possible race between partition exchange and prepare/finish requests Key: IGNITE-3464 URL: https://issues.apache.org/jira/browse/IGNITE-3464 Project:

Re: Cache performance for LOCAL mode + setIndexedTypes

I guess updating indexes is not free. Sergi On Mon, Jul 11, 2016 at 11:48 PM, AndreyVel wrote: > Hello, I have created simple test for testing performance put operations > on single computer, > can anybody explain why performance for LOCAL mode different for Indexed > and non Indexed mode? > >

Cache performance for LOCAL mode + setIndexedTypes

Hello, I have created simple test for testing performance put operations on single computer, can anybody explain why performance for LOCAL mode different for Indexed and non Indexed mode? Cache performance put(Integer, String)/sec: one client and 2 remote servers. CacheMode TR

Re: Apache Ignite - New Release

Yakov, Good idea. Alexey, Why not just bump it to 1.7 as we do usually? Sergi On Mon, Jul 11, 2016 at 9:21 PM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > There were also numerous contributions merged with small API improvements. > +1 for making a new release. > > Since the chan

Re: Apache Ignite - New Release

There were also numerous contributions merged with small API improvements. +1 for making a new release. Since the changes are mostly bugfixes, should we make it a point release?​

Cache unhandled exception

I have question about https://issues.apache.org/jira/browse/IGNITE-2079 Sametime need send notification for client listener about unhandled exception, what do you think if to add new class CacheExceptionEvent ? Maybe there is more convenient event type/name ? Server code CacheExceptionEve

Apache Ignite - New Release

Guys, We have recently found and fixed several issues in the product along with number of smaller fixes and optimizations and I would like to release these changes. Issue list follows (complete change list can be obtained via git log). ignite-3428 Fixed message recovery handling on reconnect igni

[jira] [Created] (IGNITE-3463) CPP: Add documentation for cross-platform interoperability.

Igor Sapego created IGNITE-3463: --- Summary: CPP: Add documentation for cross-platform interoperability. Key: IGNITE-3463 URL: https://issues.apache.org/jira/browse/IGNITE-3463 Project: Ignite I

Re: ignite-2310

Thanks, I updated the ticket because proposed API is ambiguous. e.g.: affinityRun(null, 0, job); The fist parameter is a collection or a cache name? My changes are at the ticket. 11.07.2016 12:59, Yakov Zhdanov пишет: I replied in the ticket. --Yakov 2016-07-11 12:43 GMT+03:00 Taras Ledkov

[jira] [Created] (IGNITE-3462) Cache is not empty after destroyCache & createCache in case Swap and EvictionPolicy used

Anton Vinogradov created IGNITE-3462: Summary: Cache is not empty after destroyCache & createCache in case Swap and EvictionPolicy used Key: IGNITE-3462 URL: https://issues.apache.org/jira/browse/IGNITE-3462

IGNITE-3055

Igniters, I have implemented timeout in DataStreamer by issue IGNITE-3055 (*IgniteDataStreamer can't be timed out*). That lead the change public API: 1) Added set and get methods (IgniteDataStreamer.timeout(long) and IgniteDataStreamer.timeout()

[GitHub] ignite pull request #866: Ignite 3424

GitHub user AndreyVel opened a pull request: https://github.com/apache/ignite/pull/866 Ignite 3424 Added unit test IgniteCacheP2pUnmarshallingContinuousQueryErrorTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

Re: ignite-2310

I replied in the ticket. --Yakov 2016-07-11 12:43 GMT+03:00 Taras Ledkov : > Hi, > > Dmitry, thanks for your comments. > I've updated the ticket with the reasons of my version of the API changes. > I'm OK with the both version of the API. > > Igniters, please any comments. > > > 09.07.2016 4:22,

[GitHub] ignite pull request #865: Ignite 3413

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

Re: ignite-2310

Hi, Dmitry, thanks for your comments. I've updated the ticket with the reasons of my version of the API changes. I'm OK with the both version of the API. Igniters, please any comments. 09.07.2016 4:22, Dmitriy Setrakyan пишет: Thanks Taras, I have added my comments in the ticket. On Thu, Jul