You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2017/08/07 09:14:00 UTC
[jira] [Created] (IGNITE-5952) Need to refactor
IgniteSystemProperties
Yakov Zhdanov created IGNITE-5952:
-------------------------------------
Summary: Need to refactor IgniteSystemProperties
Key: IGNITE-5952
URL: https://issues.apache.org/jira/browse/IGNITE-5952
Project: Ignite
Issue Type: Improvement
Reporter: Yakov Zhdanov
Priority: Minor
I would think of introducing enum each member of one should clearly define:
# name and envvar/sysprop name to set
# type
# default value
# additional methods for parsing and validation
# documentation, possibly, with links to code
This should help to avoid situations like this:
org.apache.ignite.internal.IgniteKernal#PERIODIC_STARVATION_CHECK_FREQ and org.apache.ignite.IgniteSystemProperties#IGNITE_STARVATION_CHECK_INTERVAL. Here property and its default are defined with different properties and default is not stated in configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)