Ignite's PRIMARY KEY does not map to H2 PRIMARY KEY constraint so you not seeing a primary key in H2 is OK.
Ignite's PRIMARY KEY designates a binary object that Ignite SQL Grid will create for the underlying data grid cache key. Thus, in your example you will end up with two binary objects stored in Ignite - a key with fields org_id, drug_id and prctype and a value including all the remaining fields. Now if you want to map it to Java classes KTest and TTest you have to create corresponding Java classes and give the same field names as those in the TEST table. After that you can use both Java API and SQL API to manipulate the data.
