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
So how should we work around it now? Just create a new index for
(customer_id, date)?
Cheers,
Eugene
On Mon, Sep 17, 2018 at 10:52 AM Stanislav Lukyanov
wrote:
> Hi,
>
>
>
> The thing is that the PK index is currently created roughly as
>
> CREATE INDEX T(_key)
>
> and not
>
> CREATE IN
Hi,
The thing is that the PK index is currently created roughly as
CREATE INDEX T(_key)
and not
CREATE INDEX T(customer_id, date).
You can’t use the _key column in the WHERE clause directly, so the query
optimizer can’t use the index.
After the IGNITE-8386 is fixed the index will be cre
