You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2021/10/27 15:36:00 UTC
[jira] [Updated] (IGNITE-15841) Ignite node starts with a default
configuration in case of the user-provided configuration cannot be properly
parsed
[ https://issues.apache.org/jira/browse/IGNITE-15841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vyacheslav Koptilin updated IGNITE-15841:
-----------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Ignite node starts with a default configuration in case of the user-provided configuration cannot be properly parsed
> --------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-15841
> URL: https://issues.apache.org/jira/browse/IGNITE-15841
> Project: Ignite
> Issue Type: Bug
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> In case of the user-provided configuration is broken (for example, it is an incorrect JSON file), Ignite node still tries to start with a default configuration.
> {noformat}
> Unable to read user specific configuration, default configuration will be used: ...{noformat}
> It does not seem this behavior is correct. The implementation should throw an exception with an appropriate message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)