ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolai Kulagin (JIRA)" <j...@apache.org>
Subject ***UNCHECKED*** [jira] [Updated] (IGNITE-896) Configuration inconsistency
Date Wed, 19 Sep 2018 09:09:01 GMT

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

Nikolai Kulagin updated IGNITE-896:
-----------------------------------
    Fix Version/s: 2.8

> Configuration inconsistency
> ---------------------------
>
>                 Key: IGNITE-896
>                 URL: https://issues.apache.org/jira/browse/IGNITE-896
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: sprint-5
>            Reporter: Valentin Kulichenko
>            Assignee: Nikolai Kulagin
>            Priority: Minor
>              Labels: Usability
>             Fix For: 2.8
>
>
> I noticed that some entities on cache configuration are configured via factories, while
others are set directly. For example, we use factory for ExpiryPolicy, but not for EvictionPolicy,
which looks inconsistent. Since factory-based approach comes from JCache, I think we should
use it wherever possible.
> Here is the list of settings that need to be fixed:
> * Affinity
> * AffinityMapper
> * EvictionFilter
> * EvictionPolicy
> * CacheInterceptor
> * TopologyValidator
> Need to add new configuration properties that use factories and deprecate old ones (do
not remove for compatibility).
> Also need to check other configuration beans (list above is for cache config only).



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

Mime
View raw message