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

ASF GitHub Bot commented on IGNITE-8717:
----------------------------------------

GitHub user antonovsergey93 opened a pull request:

    https://github.com/apache/ignite/pull/5625

    IGNITE-8717 Cache configuration was moved to metastore

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8717

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5625.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5625
    
----
commit d95e8a78f1e71174c130b3b9bbc89f686e6f35ff
Author: Sergey Antonov <antonovsergey93@...>
Date:   2018-11-20T13:42:46Z

    IGNITE-8717 Move cache configuration to metastore.

commit 22dc40f634e502cef32c72512db7647cfcdf1e9e
Author: Sergey Antonov <antonovsergey93@...>
Date:   2018-11-20T13:43:39Z

    IGNITE-8717 Move cache configuration to metastore.

commit be9ea5710d680bb7be791ee0c3be4abedc575309
Author: Sergey Antonov <antonovsergey93@...>
Date:   2018-11-20T15:20:48Z

    IGNITE-8717 Add GridCacheConfigurationVersion and tests for it.

commit c2441d1ae63ec6f86f7a0089c5c03df483d858a3
Author: Sergey Antonov <antonovsergey93@...>
Date:   2018-12-10T14:53:17Z

    Merge branch 'master' into ignite-8717

----


> Move persisted cache configuration to metastore
> -----------------------------------------------
>
>                 Key: IGNITE-8717
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8717
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Goncharuk
>            Assignee: Sergey Antonov
>            Priority: Major
>
> Currently, we persist cache configuration to local files which resulted in 
> several inconsistencies when a node misses configuration update (create 
> index, cache destroy, etc).
> I think the cache configuration should be saved to the metastore the same way 
> as baseline topology is saved. Same mechanics should be used for conflicting 
> configuration updates resolution.
> Along with cache configuration, it also makes sense to move marshaller and 
> binary metadata to the metastore.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to