ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5458) Add CacheKeyConfiguration to CacheConfiguration
Date Wed, 14 Jun 2017 15:30:02 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049297#comment-16049297

ASF GitHub Bot commented on IGNITE-5458:

Github user devozerov closed the pull request at:


> Add CacheKeyConfiguration to CacheConfiguration
> -----------------------------------------------
>                 Key: IGNITE-5458
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5458
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>              Labels: important
>             Fix For: 2.1
> Currently affinity column of certain type is not known on startup, as types are registered
dynamically. For this reason affinity column could be resolved incorrectly if needed before
type is registered. E.g. this is the case for our H2 tables, which need affinity key column
on startup.
> This could be resolved by setting {{IgniteConfiguration.cacheKeyConfiguration}} property,
which maps type name to affinity key column name. However, this mechanism is not flexible
enough because mappings cannot be changed in runtime.
> We should add similar property to cache configuration and use it to resolve affinity
column. Ideally, affinity key should be removed from {{BinaryType}} at all.
> Discussion on the dev list: https://mail-archives.apache.org/mod_mbox/ignite-dev/201706.mbox/browser

This message was sent by Atlassian JIRA

View raw message