[jira] [Reopened] (IGNITE-15369) Fix behavior when using @AffinityKeyMapped

["Maksim Timonin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-15369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Timonin reopened IGNITE-15369:
-------------------------------------

Non-duplicate. 

Issue:
 # Declare PersonKey (@QuerySqlField id, @AffinityKeyMapped cityId)
 # Declare QueryEntity (PersonKey, Person)
 # It's required QueryEntity.setKeyFields(id, cityId). 

It's wanted to avoid step #3

 

> Fix behavior when using @AffinityKeyMapped
> ------------------------------------------
>
>                 Key: IGNITE-15369
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15369
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Luchnikov Alexander
>            Priority: Minor
>              Labels: ise
>         Attachments: AffinityKeyMappedTest.java
>
>
> When creating a cache from a thin client, which will store instances of classes annotated with @AffinityKeyMapped, you must additionally configure QueryEntity, otherwise the affinity key information will not be included in the h2 meta.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)