[
https://issues.apache.org/jira/browse/IGNITE-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466176#comment-16466176
]
Ilya Kasnacheev commented on IGNITE-8448:
-----------------------------------------
Currently, a workaround should be available by setting
cacheConfiguration.setKeyConfiguration() to a custom CacheKeyConfiguration (in
Java config or XML).
But it would be more direct to just be able to specify affinity key in C++.
Otherwise, a following error is reported:
{code}
An error occurred: Java exception occurred
[cls=org.apache.ignite.binary.BinaryObjectException, msg=Binary type has
different affinity key fields [typeName=KeyType, affKeyFieldName1=affId,
affKeyFieldName2=null]]
{code}
> C++: AffinityKey support
> ------------------------
>
> Key: IGNITE-8448
> URL: https://issues.apache.org/jira/browse/IGNITE-8448
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
> Affects Versions: 2.6
> Reporter: Ilya Kasnacheev
> Assignee: Vladimir Ozerov
> Priority: Major
>
> Add AffinityKey class and AffinityKeyMapped attribute to allow custom
> affinity mapping.
> This is crucial for SQL joins to work properly.
> See org.apache.ignite.cache.affinity.AffinityKey and AffinityKeyMapped in
> Java.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)