Hello! Please use !set outputFormat vertical to see complete execution plan.
Index is created on primary key. There is no programmatic way to change its inline size other than specifying IGNITE_MAX_INDEX_PAYLOAD_SIZE system property or environment variable. If it is of complex type, some versions may not be able to search by its fields. Regards, -- Ilya Kasnacheev чт, 18 июн. 2020 г. в 13:13, narges saleh <[email protected]>: > Hi All, > > Shouldn't primary keys result in indexes and if so, shouldn't I be able to > see them when I list indexes? > Does inline index size applicable to primary keys too? > Additionally, when I do explain plan on a query which involves tables with > primary keys, shouldn't I see the primary key/index being used? Or lack of > a scan statement imply that an index is being used? > -------+ > | PLAN | > +--------------------------------+ > | SELECT > ID, NAME,TIMESTAMP > FROM PUBLIC.table1 > /* PU | > > sql is: select timestamp from table1 where id = 50 and name = 'John'; > //primary key is on id + name >
