You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kuznetsov (JIRA)" <ji...@apache.org> on 2015/03/18 09:58:38 UTC

[jira] [Assigned] (IGNITE-375) Add limited support for primitive keys in CacheJdbcStore

     [ https://issues.apache.org/jira/browse/IGNITE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kuznetsov reassigned IGNITE-375:
---------------------------------------

    Assignee: Andrey Novikov  (was: Alexey Kuznetsov)

Please add test with Date and Timestamp and merge

> 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
>             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)