Hello!

1) Neither of tickets is not RESOLVED so you probably can't.

2) I have failed to observe this problem:

0: jdbc:ignite:thin://localhost> CREATE TABLE public.transactions (pk INT,
id INT, k VARCHAR, v VARCHAR,
. . . . . . . . . . . . . . . .> PRIMARY KEY (pk, id));
No rows affected (0,182 seconds)
0: jdbc:ignite:thin://localhost> CREATE INDEX transactions_id_k_v ON
public.transactions (id, k, v)
. . . . . . . . . . . . . . . .> INLINE_SIZE 100;
No rows affected (0,043 seconds)
0: jdbc:ignite:thin://localhost> !indexes
TABLE_CAT         IGNITE
TABLE_SCHEM       PUBLIC
TABLE_NAME        TRANSACTIONS
NON_UNIQUE        true
INDEX_QUALIFIER
INDEX_NAME        TRANSACTIONS_ID_K_V
TYPE              3
ORDINAL_POSITION  1
COLUMN_NAME       ID
ASC_OR_DESC       A
CARDINALITY       0
PAGES             0
FILTER_CONDITION

TABLE_CAT         IGNITE
TABLE_SCHEM       PUBLIC
TABLE_NAME        TRANSACTIONS
NON_UNIQUE        true
INDEX_QUALIFIER
INDEX_NAME        TRANSACTIONS_ID_K_V
TYPE              3
ORDINAL_POSITION  2
COLUMN_NAME       K
ASC_OR_DESC       A
CARDINALITY       0
PAGES             0
FILTER_CONDITION

TABLE_CAT         IGNITE
TABLE_SCHEM       PUBLIC
TABLE_NAME        TRANSACTIONS
NON_UNIQUE        true
INDEX_QUALIFIER
INDEX_NAME        TRANSACTIONS_ID_K_V
TYPE              3
ORDINAL_POSITION  3
COLUMN_NAME       V
ASC_OR_DESC       A
CARDINALITY       0
PAGES             0
FILTER_CONDITION

Regards,
-- 
Ilya Kasnacheev


пн, 4 февр. 2019 г. в 19:33, joseheitor <[email protected]>:

> Thanks, Ilya.
>
> 1. - I see that this issue has been addressed - should I be able to verify
> this by pulling the latest nightly-build?
>
> 2. - Issuing the following statement via a JDBC application or with a JDBC
> client, such as DBeaver, results in the index being created, but only on
> the
> 2nd and 3rd specified columns (only tested with JDBC Thin Client):
>
> Assuming a table with the following structure:
> CREATE TABLE public.transactions (pk INT, id INT, k VARCHAR, v VARCHAR,
> PRIMARY KEY (pk, id))
>   WITH "TEMPLATE=PARTITIONED, BACKUPS=1, ATOMICITY=TRANSACTIONAL_SNAPSHOT,
> WRITE_SYNCHRONIZATION_MODE=FULL_SYNC, AFFINITY_KEY=id";
>
>
> *CREATE INDEX transactions_id_k_v ON public.transactions (id, k, v)
> INLINE_SIZE 100;*
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1652/index-missing-first-column.png>
>
>
> 3. - [Apologies] Please ignore - it appears to be working correctly!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to