[IGNITE-10602] Failure parsing INLINE_SIZE if CREATE INDEX is one of multiple statements

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.7
• Fix Version/s: 2.8
• Component/s: sql
• Assignee: Pavel Kuznetsov
• Reporter: Ilya Kasnacheev
• Created: 07/Dec/18 16:37
• Updated: 08/Feb/19 09:26
• Resolved: 08/Feb/19 08:10

Description

On an empty cluster issue the following statements (shown using sqlline):

0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT, id INT, k
. . . . . . . . . . . . . . . .> VARCHAR, v VARCHAR, PRIMARY KEY (pk, id)); CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v) INLINE_SIZE 150; CREATE INDEX transactions_k_v_id ON
. . . . . . . . . . . . . . . .> public.transactions (k, v, id) INLINE_SIZE 150; CREATE INDEX transactions_pk_id ON public.transactions
. . . . . . . . . . . . . . . .> (pk, id) INLINE_SIZE 20;

Expected: Table is created, three indexes are created.
Actual: table is created, indexes are NOT created, error is printed:
Error: Failed to parse query. Синтаксическая ошибка в выражении SQL "CREATE INDEX TRANSACTIONS_ID_K_V ON PUBLIC.TRANSACTIONS (ID, K, V) INLINE_SIZE[*] 150; CREATE INDEX TRANSACTIONS_K_V_ID ON

Issue Links

• is caused by: IGNITE-6850 SQL: integrate index inline size to CREATE INDEX syntax
• is duplicated by: IGNITE-10063 MVCC SQL: Tx SQL commands are not supported in multistatements
• links to: GitHub Pull Request #6018
• links to: Userlist thread