Hi, Igniters. There was know issue described at the [IGNITE- 16098] case 1. These issue is the cause of not symmetric cache API and SQL API: we cannot create the same table by SQL and cache API (with se identical internal structures). In more detail: it is impossible now to create a sorted PK index with unwrapped fields through cach eAPI.
I think it's more convenient when SQL and the cache API have equal capabilities. Also I found the second scenario that can break indexes. Please take a look at the issue [1] description, and let me know what you think. [1]. https://issues.apache.org/jira/browse/IGNITE-16098
