Hi Folks.
I checked the JDBC driver support docs..Is it true to say that if i have a
grid with say 10 ignite caches (caching 10 different tables in DB) can i
just connect to the grid (having it all specified in the config xml &
execute queries on any/all of them including queries that join from
Hi,
I am not sure if you got a chance to go though my emailas i stated
there i intentionally did that as a test for one of the inserts to fail to
verify if the entire transaction involving inserts to two tables gets
rolled back both in the cache & in the DB. As i observed it doesn't seem to
Because you are trying to insert employee with same name and you do have
constraint for it .
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value
violates unique constraint "dcm_emp_ename"
Detail: Key (ename)=(Jacky) already exists.
On Thu, Jun 22, 2017 at 8:35 PM, Muthu
Hello Folks,
I tried the Ignite spring transactions integration by using
*CacheSpringStoreSessionL**istener* (i used it with Ignite web console
based Automatic Persistence).
I see that Transactional writes seems to fail & does not seem to work as
expected (one table/cache was inserted while
Has anyone measured x86 instruction count needed by a single cache
insert/update once it gets to the correct data node? Lets say for String key
and value or String key and object value with a couple of scalar members.
--
View this message in context:
AffinityKeyMapped is only processed on cache keys, not on cache values.
Try cache.put(keyEntityWithAffinityKeyMappedAnnotation, value)
El 22 jun 2017, a las 13:16, tuco.ramirez [via Apache Ignite Users]
>
escribió:
Hi,
Hi,
Then just make it *volatile* like this "private *volatile* IgniteCache cache;"
Kind regards,
Alex.
On Thu, Jun 22, 2017 at 3:21 PM, mdolgonos [via Apache Ignite Users] <
ml+s70518n14045...@n6.nabble.com> wrote:
> Thank you, Alex, for your response.
> However, this
>> skuMap.put(i, item);
You are not using the TestItem as a key to the map but rather a counter thus
the results that you are seeing.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Affinity-key-does-not-seem-to-be-working-tp14043p14044.html
Sent from the
Hi,
I have a simple use case, but affinity key does not seem to be working.
AffinityKey is placed on clientId which is same for everyone. So all the
data should go to one node.
However ignite visor shows that the data is different on each nodes, with
each node having 3000+ entries.
using 1.9.0
Hi,
Please check if making cache field final will help you. There could be a
problem with inter-thread visibility.
Try changing the field signature to "private *final* IgniteCache cache;"
Kind regards,
Alex.
On Thu, Jun 22, 2017 at 1:10 AM, mdolgonos [via Apache Ignite
Hi,
Could you please share your test project?
Thanks!
-Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p14041.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
I've replicated this behavior in a test.
My setup:
2 server nodes
1 client node
I used 3 IDEs to run this this test (1 running each node). First I startup
the 2 server nodes (via the startServerNode and startServerNode2 test
methods), then I startup the client node (viathe startClientNode
12 matches
Mail list logo