Multi-cache transactions & persistent store

Hi guys, Playing with Ignite multi-cache transactions(transactions involving multiple caches) we run into the lack of proper/easy mechanism to support such transactions on persistent store side (while implementing particular *CacheStore*). The problem is there is no easy way for *CacheStore

Re: Batch support in Cassandra store

Hi Valentin, Sounds reasonable. I'll create a ticket to add Cassandra logged batches and will try to prepare some load tests to investigate if unlogged batches can provide better performance. Will also add ticket for RAMP as a long term enhancement. Igor Rudyak On Fri, Jul 29, 2016 at 5:45 PM,

Re: Batch support in Cassandra store

Hi Igor, 1) Yes, I'm talking about splitting the entry set into per-partition (or per-node) batches. Having entries that are stores on different nodes in the same batch doesn't make much sense, of course. 2) RAMP looks interesting, but it seems to be a pretty complicated task. How about adding

Re: Batch support in Cassandra store

Hi Valentin, 1) According unlogged batches I think it doesn't make sense to support them, cause: - They are deprecated starting from Cassandra 3.0 (which we are currently using in Cassandra module) - According to Cassandra documentation (

Re: JetBrains Annotaions usage.

Alexey, thanks for tips. Seems maven dependency's "optional" tag can handle this. See pullrequest for details. P.s. I'm not pretty sure this change will not brake something, need to recheck it twice. On Thu, Jul 28, 2016 at 5:15 PM, Alexey Goncharuk <

[GitHub] ignite pull request #909: JB Annotatins required only at Ignite sources comp...

GitHub user avinogradovgg opened a pull request: https://github.com/apache/ignite/pull/909 JB Annotatins required only at Ignite sources compilation time. You can merge this pull request into a Git repository by running: $ git pull https://github.com/avinogradovgg/ignite

Re: Apache Ignite - New Release

On Fri, Jul 29, 2016 at 9:17 AM, Pavel Tupitsyn wrote: > Guys, I can handle upcoming 1.7 release and send the vote next week, if > there are no objections. > Thanks Pavel! I don't think anyone will have any objections. Given that you will be a manager for this release,

[jira] [Created] (IGNITE-3608) QuerySqlFunction methods with Object type var args do not work

Edward Kaganovich created IGNITE-3608: - Summary: QuerySqlFunction methods with Object type var args do not work Key: IGNITE-3608 URL: https://issues.apache.org/jira/browse/IGNITE-3608 Project:

Re: Apache Ignite - New Release

Guys, I can handle upcoming 1.7 release and send the vote next week, if there are no objections. Pavel. On Thu, Jul 28, 2016 at 12:36 AM, Dmitriy Setrakyan wrote: > On Wed, Jul 27, 2016 at 4:00 AM, Semyon Boikov > wrote: > > > Dmitry, all Ignite

[jira] [Created] (IGNITE-3607) Send non-filtered continuous query notifications in one message per client

Alexey Goncharuk created IGNITE-3607: Summary: Send non-filtered continuous query notifications in one message per client Key: IGNITE-3607 URL: https://issues.apache.org/jira/browse/IGNITE-3607

Re: Deadlock during Client Continuous Query deserialization

Here is JIRA issue: https://issues.apache.org/jira/browse/IGNITE-3606 On Fri, Jul 29, 2016 at 5:48 PM, Semyon Boikov wrote: > Hi, > > I reproduced this issue, thank you for test! After quick debugging It > seems that this is some problem with Ignite backpressure mechanism

[jira] [Created] (IGNITE-3606) Node sometimes fails to detect broken connection

Semen Boikov created IGNITE-3606: Summary: Node sometimes fails to detect broken connection Key: IGNITE-3606 URL: https://issues.apache.org/jira/browse/IGNITE-3606 Project: Ignite Issue

[jira] [Created] (IGNITE-3605) Commits\rollbacks count is ZERO for transactional cache in case if the load generated by client node

Pavel Konstantinov created IGNITE-3605: -- Summary: Commits\rollbacks count is ZERO for transactional cache in case if the load generated by client node Key: IGNITE-3605 URL:

[jira] [Created] (IGNITE-3604) .NET: Inconsistent namespace imports in examples

Pavel Tupitsyn created IGNITE-3604: -- Summary: .NET: Inconsistent namespace imports in examples Key: IGNITE-3604 URL: https://issues.apache.org/jira/browse/IGNITE-3604 Project: Ignite Issue

Re: Documentation for IGNITE-3399 (Support primitive type names in QueryEntity)

Hi Pavel, yes that's correct re "int". Thanks for the info. Thanks Jens On Thu, Jul 28, 2016 at 1:29 PM, Pavel Tupitsyn wrote: > Hi, > > Do I understand correctly that we can now replace > > with > > in QueryEntity.fields? > > There are Spring XML examples on

Re: Batch support in Cassandra store

Hi Igor, I'm not a big Cassandra expert, but here are my thoughts. 1. Sending updates in a batch is always better than sending them one by one. For example, if you do putAll in Ignite with 100 entries, and these entries are split across 5 nodes, the client will send 5 requests instead of 100.