[
https://issues.apache.org/jira/browse/IGNITE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov resolved IGNITE-375.
-----------------------------------
Assignee: Alexey Kuznetsov
Add support UUID in branch ignite-375
> 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: Alexey Kuznetsov
> Fix For: sprint-2
>
>
> 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)
