Yep, just create a separate index.
(I saw in your other messages that you’re already trying that)
Stan
From: eugene miretsky
Sent: 18 сентября 2018 г. 17:56
To: user@ignite.apache.org
Subject: Re: IGNITE-8386 question (composite pKeys)
So how should we work around it now? Just create a new
will behave the way you expect (e.g. it will be used instead of
> the affinity key index).
>
>
>
> Stan
>
>
>
> *From: *eugene miretsky
> *Sent: *12 сентября 2018 г. 23:45
> *To: *user@ignite.apache.org
> *Subject: *IGNITE-8386 question (composite
created as a multi-column
index, and will behave the way you expect (e.g. it will be used instead of the
affinity key index).
Stan
From: eugene miretsky
Sent: 12 сентября 2018 г. 23:45
To: user@ignite.apache.org
Subject: IGNITE-8386 question (composite pKeys)
Hi,
A question regarding
https
Hi,
A question regarding
https://issues.apache.org/jira/browse/IGNITE-8386?focusedCommentId=16511394&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16511394
It states that a pkey index with a compoise pKey is "effectively useless".
Could you please explain why is
