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

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

GitHub user dream-x opened a pull request:

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

    IGNITE-2558: Remove extends MutableConfiguration, add setCopyOnRead method.

    [Jira](https://issues.apache.org/jira/browse/IGNITE-2558)

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

    $ git pull https://github.com/dream-x/ignite ignite-2558

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

    https://github.com/apache/ignite/pull/1701.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 #1701
    
----
commit 3ecd24102e87650ea944642a1002fbcedc51a626
Author: Max Kozlov <dreamx....@gmail.com>
Date:   2017-03-30T12:19:17Z

    Remove extends MutableConfiguration, add setCopyOnRead method.

----


> NearCacheConfiguration should not extend MutableConfiguration
> -------------------------------------------------------------
>
>                 Key: IGNITE-2558
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2558
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Valentin Kulichenko
>            Assignee: Maksim Kozlov
>             Fix For: 2.0
>
>
> Currently {{NearCacheConfiguration}} extends {{MutableConfiguration}} which 
> means that it inherits all the properties that don't make sense for it. Also 
> it's possible to use it to create a cache with {{CacheManager}}, which is 
> also confusing.
> {{NearCacheConfiguration}} should not extend and classes and should be used 
> only directly in {{CacheConfiguration.setNearConfiguration()}} or 
> {{Ignite.createCache()}} and similar methods.
> In addition, it would be useful to add {{setCopyOnRead}} property for near 
> cache. Now it's not possible to control this behavior for near cache only.



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

Reply via email to