ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-896) Configuration inconsistency
Date Tue, 12 May 2015 18:39:01 GMT
Valentin Kulichenko created IGNITE-896:
------------------------------------------

             Summary: 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
            Priority: Minor
             Fix For: sprint-5


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
(v6.3.4#6332)

Mime
View raw message