Hello! 1. This is certainly possible since we have at least on issue about CREATE INDEX in multiple statemen queries:
https://issues.apache.org/jira/browse/IGNITE-10602 2. This is strange since this scenario is routinely uses. Do you have reproducer? How do you determine that index does not contain `id'? 3. Do you have reproducer for this case? Note that recently there were some troubles with index name capitalization, maybe that's the culprit. https://issues.apache.org/jira/browse/IGNITE-11146 Regards, -- Ilya Kasnacheev пн, 4 февр. 2019 г. в 08:10, joseheitor <[email protected]>: > Hi Ignite Team, > > Here are three issues that I have picked up on a 2.8 nightly build (don't > know if these have been reported and logged previously...?): > > Version: 2.8 > Build: 20181226 > > *Issue 1:* > > CREATE INDEX statements cannot be part of an SQL multi-statement. But they > can be executed individually. > > *Issue 2:* > > CREATE INDEX ignores first column of a multi-column index. For example... > > CREATE INDEX multi_index ON public.table (id, k, v) INLINE_SIZE 100; > > results in an index for columns 'k' and 'v' only. > > *Issue 3:* > > DROP INDEX IF EXISTS... fails > DROP INDEX... works ok > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
