You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Andrey Novikov (JIRA)" <ji...@apache.org> on 2015/02/27 16:43:04 UTC
[jira] [Created] (IGNITE-375) Add limited support for primitive
keys in CacheJdbcStore
Andrey Novikov created IGNITE-375:
-------------------------------------
Summary: Add limited support for primitive keys in CacheJdbcStore
Key: IGNITE-375
URL: https://issues.apache.org/jira/browse/IGNITE-375
Project: Ignite
Issue Type: Improvement
Reporter: Andrey Novikov
Assignee: Andrey Novikov
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".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)