Re: 3rd Party Persistence and two phase commit

Local store = Apache Ignite Native Persistence? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 3rd Party Persistence and two phase commit

Hi, Aleksey, what is "local db"? I did not find anything on this in the documentation. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: 3rd Party Persistence and two phase commit

Hi Aleksey, thanks for info, "/Actually, data could be persisted not on tx initiating node, but on primary(I.e. we have partitioned cache and local cache)/" Ok, but no matter where the data is persisted, there will always be only 1 database connection within the transaction, no matter how many

Re: 3rd Party Persistence and two phase commit

Hi Denis, Yes, I have already read the article you mentioned. But it shows an example where the primary data being changed is located on the same node, at least I understand it so. In my original understanding it was that each node creates its own connection to the 3rd database. But perhaps

Re: 3rd Party Persistence and two phase commit

Hi Denis, thanks for clarifying! Did I understand you correctly that in any cases all interactions with 3rd party database will occur only on the initial node and the sessionEnd method will be called only once on the initial node? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

3rd Party Persistence and two phase commit

Hi all! We have a cache "Accounts". We use 3rd Party Persistence with Write-Through mode In the cache there are two accounts. Account width id = 1 is located on node A and account with id = 2 is located on node B. In a single transaction we want to transfer the amount of $100 from account 1 to

Re: Issue with running SQL Scan queries

Hi, try to enable peerClassLoading add to node config -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Issue-with-running-SQL-Scan-queries-tp2753p2757.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Sql query performance with partitioned caches

Hi All, "use Ignite exactly for OLTP workloads" I mean SQL OLTP workloads. I have no doubt that the OLTP workloads using direct cache API calls ignite scales perfectly. But not to argue in vain, I will use the well-tested method - benchmarking. Thank you for your responses. -- View this

"Read-through" implementation for sql query

Hi All, Can somebody explain how the mode "Read-through" works if I execute the query(below) suppose twice? Assume that initially the cache is empty. The sql query is: select name from person where name like "t*" -- View this message in context:

Re: "Read-through" implementation for sql query

Hi Alexey, Do I understand correctly that this is true for all Query.class subclasses? Ok, if cache doesn't contain key k, then all call get(k) will trigger read=through functionality? Thanks. -- View this message in context:

Re: Sql query performance with partitioned caches

Denis, Do not take the examples as the real problem. In real application sql can be more complex like this: select a.* from account a join account_details b on (b.id = a.id) where b.type = 'TTT' and (select nvl(sum(amount),0) from account_sums s where s.id = a.id) > 0 and a.id = 1

Re: Sql query performance with partitioned caches

Hi Valentin, 1. We have partitioned cache "myCache" where store entities like Account(id, name) 2. key = id e.g. cache.put(1, new Account(1,"account 1")); 3. Assume I execute throuth jdbc query "select * from account where id=1", i want that query doesn't broadcast on every node. -- View this

Re: Sql query performance with partitioned caches

Hi Valentin, The proposed option is not suitable. In most cases, the application does not know on which node and in which partition the data resides, as it is the physical layer of data model, which can change over time (application only knows the logical data model). The application simply

Cross join bug for partitioned caches

Hi all! Testing ignite 1.5. Seems, cross join on partitioned caches, when started more then 1 server node return incorrect result (part of the rows is missing). When started only one server node or caches in replicated mode all work correctly. -- View this message in context:

Re: Sql query performance with partitioned caches

Hi Dmitriy, How about query that returns or scans less 1% of the rows (or only one row), and the rows that satisfy the query predicates all resides on one node? When we add nodes, such queries become slowly. Are there any plans for implementing for sql queries any kind of partitions or/and nodes

Re: Cross-cache query between replicated and partitioned caches

Hi, You must start(attach) your query on partition cache not replicated. cache.query() // cache must be partition cache -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cross-cache-query-between-replicated-and-partitioned-caches-tp2698p2707.html Sent from the

Re: Sql Query using Map as value for cache

Hi Val, BinaryObject is what I was looking for. I've tested it and it suits for my task. Thank you very mach! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Sql-Query-using-Map-as-value-for-cache-tp2668p2688.html Sent from the Apache Ignite Users mailing list

Re: Sql Query using Map as value for cache

Hi, thanks for response! /"Maps should be compared using equals() method implementation and sorted (maps instances) according to compareTo() method/" I do not quite understand what the problem is, is POJO do not need to do the same? My usecase is to create new queryable caches (queryable by sql

Re: Affinity Key??

Hi! You can gather more information about affinity after reading the javadoc for classes http://ignite.apache.org/releases/1.5.0-b1/javadoc/org/apache/ignite/cache/affinity/AffinityFunction.html

Sql Query using Map as value for cache

Hi! Testing Ignite 1.5.0. Can we use Query, QueryIndexes over caches where values is a Map.class subclasses? Or its possible only for POJO as a value? Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Sql-Query-using-Map-as-value-for-cache-tp2668.html