ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-375) Add limited support for primitive keys in CacheJdbcStore
Date Thu, 12 Mar 2015 07:46:40 GMT

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

Alexey Kuznetsov closed IGNITE-375.
-----------------------------------
    Assignee:     (was: Alexey Kuznetsov)

Fixed as part of IGNITE-329 and IGNITE-330

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

Mime
View raw message