ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5411) Persist affinity key on disk
Date Tue, 06 Jun 2017 10:22:18 GMT

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

Vladimir Ozerov commented on IGNITE-5411:
-----------------------------------------

I thought a bit more on this problem, and it seems that we'd better to save information about
affinity column near cache configuration.

> Persist affinity key on disk
> ----------------------------
>
>                 Key: IGNITE-5411
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5411
>             Project: Ignite
>          Issue Type: Task
>          Components: binary
>            Reporter: Vladimir Ozerov
>             Fix For: 2.1
>
>
> Currently binary metadata is not persisted on a disk anyhow. It means that after full
cluster restart we will loose all runtime metadata (except of those configured explicitly
in {{IgniteConfiguration.binaryConfiguration}}.
> In future releases we will store metadata in separate storage. For now I propose only
to store typeId -> affinityKey mapping on disk to improve value of {{CREATE TABLE}} feature
where affinity key is essential for data co-location.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message