Hi! Current implementation of org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore requires to have two classes in type metadata: key class and value class (PersonKey and Person for example).
But in most cases key class is just a wrapper over primitive key and in case of *ONE type per cache *it will be useful to allow primitive (Integer, Long, String,...) type as key (Integer and Person for example). If user will try to register in CacheTypeMetadata more than one class with same primitive key we will throw exception like this "Only single type per cache allowed with same key class". Thoughts? -- Alexey Kuznetsov GridGain Systems www.gridgain.com
