Re: Afinity Key

This discussion seems to be a complete duplicate of this one: http://apache-ignite-users.70518.x6.nabble.com/Affinity-td9744.html. Let's continue there. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Afinity-Key-tp9774p9804.html Sent from the Apache Ign

Re: Affinity

Anil, Can you create a unit test that will demonstrate the problem? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-tp9744p9803.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Partitions within single node in Apache Ignite

Hi, This is possible with Scan query only. Use ScanQuery.setPartition(..) method to specify a partition you want to scan. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Partitions-within-single-node-in-Apache-Ignite-tp9726p9802.html Sent from the Apache I

Re: Scan query vs Sql query

If you know that you are going to scan the whole cache anyways, then probably SCAN queries will perform better. SQL allows you to index fields or even groups of fields and do lookups much faster. Sergi 2016-12-29 10:22 GMT+03:00 rishi007bansod : > From performance point of view which type of que

Re: Afinity Key

Hi , Scenario is : Person cache -> AffinityKey(personId, equivalentid) PersonDetail cache -> AffinityKey(detailId, equivalentid) both caches joined on equivalentId and collated is set to true in jdbc url. Did I miss anything ?? Query will be: SELECT p.*, m.* from person p join PERSONDETAILS

Re: Afinity Key

Could you give example of your query? I will try to reproduce. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Afinity-Key-tp9774p9799.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Affinity

Hi Val, I did the same and seems join is not providing all the cache entries. Person cache -> AffinityKey(personId, equivalentid) PersonDetail cache -> AffinityKey(detailId, equivalentid) both caches joined on equivalentId and collated is set to true in jdbc url. Did I miss anything ? i see oth

Re: Make changes to cache entry before data rebalanicng.

Well, i am running ignite nodes on an "alien"(meh) architecture. JVM implementation there has high latency when accessing data in memory, so i am trying to move my data to c++ side of my code and then run some processing on it. So my idea was to implement my own Marshaller wich would "strip" my dat

Re: Afinity Key

Yes sure , I have one cache1 with some records and Cache2 with some more records both cache are related to each other through eqID. I am trying to collocate both cache by using below code snippet. cache1.put(new AffinityKey<>(*pk0*, eqID),value1); cache2.put(new AffinityKey<>(*pk1*, eqID), valu

Re: IgniteDataStreamer with Continuous Query

Hi, In my test case scenario I am pumping data into cache via data streamer which has Created expiration policy of 60 seconds to have sliding window of 60 seconds, after the initial bursts I am making my thread to sleep then again pump data, but for the 2nd bursts I am not getting any events (local

Re: Afinity Key

Yes, that's right. Could you, please, describe more detailed what exact problem you faced with? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Afinity-Key-tp9774p9794.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.