Hi, Again, I understand why it is as it is. My concern was that from a design perspective it adds a dimension to the key for "technical" reasons. I wanted to make sure that it is the way to go. Thanks for thr clarification
Best Regards -------- Original Message -------- Subject: RE: Affinity not based on the fields in the key From: vkulichenko To: [email protected] CC: Hi Steve, Affinity key field must be a part of key, simply because affinity does not depend on value at all. It's not even required to have a value to calculate affinity. However, you can simply move the corresponding field from value object to key object. You can still use it in queries and it will be a part of the same table, so this doesn't actually break normal form (as a matter of fact, this doesn't change your SQL schema at all). -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Affinity-not-based-on-the-fields-in-the-key-tp9450p9490.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
