Hi 

I am using Ignite 2.3

Have 2 tables

Table 1: Customer - primary Key is PartyId
Table 2: Account - primary key is AccountID  (also has PartyID as one of the
column)

To keep both customer and account data for a customer  on the same node I
need to  use affinity key for Account table. And affinity key column should
be always part of the primary key.
So Account table will have a composite key consisting of AccountID, PartyID.

My question is, while querying the data from Account table, how does the
query work 

1. If I only pass AccountID
2. If I pass both AccountID and PartyID

if I only pass AccountID, does it treat like querying the table based on the
primary key OR I need to create an index on AccountID as well to improve the
performance. 

To keep the data unique, I dont need PartyID as part of Primary key on
Account table. Just for the sake of using Affinity functionality, I need to
use PartyID as part of Account table primary key.

Can someone answer this please?

Thanks
Naveen



Thanks
Naveen



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to