Re: transaction not timing out

Binti, Locks are acquired on prepare phase, not on commit phase. In case of optimistic transaction both phases happen one after another in a single 'tx.commit()' call. Prepare phase is not a problem, because it's easy to detect collisions and throw optimistic exception when all locks are not

Re: Re: SQL join query return different result under the same data when having different ignite instance.

Hi Val, Yes, I do the change as you suggest. Now, the tables is the following: School: id name address 1 xxx aaa Class: id name number schoolID 1 yyy bbb 1 Student: id name sex schoolID classID 1 zzz male 1 1 And the cache keys

Re: How to monitor the cache info?

Hi, Jason, I think you could use JMX to monitor various metrics of Ignite. You may start to look from classes: org.apache.ignite.mxbean.IgniteMXBean org.apache.ignite.mxbean.CacheMetricsMXBean On Mon, Jul 25, 2016 at 6:17 PM, Jason wrote: > hi Ignite team, > > In the

Re: transaction not timing out

What I mean is why would commit() hang? we use write behind, so cache store updates are asynchronous (I doubt it would be an issue in our case) during the commit() phase, if locks were not acquired on txn entries, we would receive txn optimistic exception, we do receive that sometimes, but in

Re: Re: SQL join query return different result under the same data when having different ignite instance.

Hi Bob, In this example Class table should also have schoolId field and schoolId should be used as the affinity key for all three types. This will guarantee that all data linked to a particular school resides on the same node. -Val -- View this message in context:

Re: transaction not timing out

Hi Binti, bintisepaha wrote > I do not understand why commit() is unable to finish. In an > optimistic/serializable transaction, it should not even reach the commit > phase using the 2 phase protocol. If the txn reached he commit() phase and > then it was successful in acquiring all the locks it

Re: Ignite - Using - complex object with nested attributes and search

You can't search inside a collection with SQL. Instead, you should store Person and Address separately and link them using foreign keys, similar to relational database. You can then join these two table in your SQL query. Refer to the query example [1] for more details. [1]

Re: Is there any such thing as SQlBuilder in apache Ignite for SQLQuery

You can query without OFFSET .. LIMIT and iterate through the QueryCursor, it will automatically fetch data in pages. The page size is defined by pageSize property on the query object. But this will only allow you to go forward, you will not be able to return to previous page or go to any random

Re: Rest-api: Returning no reply from server

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 chetanvyadav wrote > $ curl

Re: QuerySqlFunction methods with variable arguments do not seem to work

Val, thanks for your offer to help. The example is provided in my original post. Just register the class in your cache and set the breakpoint in the function to see if it gets called. You don't have to have any specific cache structure, just run a pure /"select affinityKey('java.lang.String',

Re: Ignite - CEP

Hi, Here are my answers. 0. Not sure about production usage, but the described approach makes sense to me. 1. Ignite is designed to be scaleable, so you just need to make sure that you have enough memory for your data. Refer to [1] for information about capacity planning. 2-3. You can simply

Re: Hazelcast vs Ignite vs Geode

On Wed, Jul 27, 2016 at 9:58 AM, Ralph Goers wrote: > That is not strictly correct. You can do objective performance testing of > Ignite and compare that to other solutions, where it is allowed (which it > typically would be for other open source solutions). When you

Re: Ignite - CEP

We are preparing to deploy Ignite as part of CEP system. We have the following components - A loader using the DataStreamer to continually push into a single - Clients registering continuous queries - Instead of using an expiration policy we are deploying a service to selectively delete

Re: Ignite - Using - complex object with nested attributes and search

You can do this using ScanQuery by passing predicate to it. Predicate will have all conditions you want to check like person.name.contains(searchparameter) For JOINS, you have to use SqlQuery but I havent tried that. On Wed, Jul 27, 2016 at 6:50 AM, M Singh wrote: > Hi: >