You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Luchnikov Alexander (Jira)" <ji...@apache.org> on 2021/08/25 13:21:00 UTC

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

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

Luchnikov Alexander updated IGNITE-15369:
-----------------------------------------
    Attachment: AffinityKeyMappedTest.java

> 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)