Hello!

I've looked at your project and seems you confised cache names. Cache
configuration contains "AccountCache" and "CustomerCache", but for
streaming you use "Customer" and "Account" caches.

On Tue, Dec 12, 2017 at 4:50 PM, Naveen <naveen.band...@gmail.com> wrote:

> Hi All
>
> Had any one got a chance look into this issue.
>
> As mentioned,  I am using Affinity key and IgniteDataStreamer to load data
> of 10M.
>
> This is how my code looks like
>
> Customer cache - PartyID is the primary key
> IgniteDataStreamer<String, Customer> streamer =
> ignite.dataStreamer("Customer"));
>
> Account cache - AccoutnID is the Primary key and also has PartyID column
> IgniteDataStreamer<AffinityKey, Account> streamer =
> ignite.dataStreamer("Account"));
> //Setting the Affinity kay
> accountKey = new AffinityKey(AccountID, PartyID);
> streamer.addData(accountKey, act);
>
> My requirement is to join customer and account with the partyID and query
> for a specific party ID, the is the query I run
>
> select P.PARTY_ID, A.PARTY_ID, P.ACCOUNT_ID_LIST from "Customer".Customer
> P,
> "Account".Account  A where P.PARTY_ID='P101000001' and P.PARTY_ID=
> A.PARTY_ID;
>
> This seems to be work without specifying the distributeJoins=true, and
> response also very fast, around 30  ms. However, I could see some data
> missing Account cache.
>
> DataLoadAffinity.java
> <http://apache-ignite-users.70518.x6.nabble.com/file/
> t1478/DataLoadAffinity.java>
>
> Have added Java cod for reference, if you want to reproduce the issue.
>
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to