[
https://issues.apache.org/jira/browse/IGNITE-13837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256558#comment-17256558
]
Sergey Chugunov commented on IGNITE-13837:
------------------------------------------
There are several points that are great to clarify in this ticket.
First, how do we want to do an actual update of configuration tree that we have
in memory? One of possible ways to simplify flow is to update it only by a
callback from storage (when the update is already accepted by storage). That
approach simplifies compare-and-set flow by making storage responsible to do an
actual cas operation.
Second, as we have storage involved into the update we need to clarify a
hierarchy of exceptions declared by API to let user code to decide how to
handle different situation.
> Configuration initialization
> ----------------------------
>
> Key: IGNITE-13837
> URL: https://issues.apache.org/jira/browse/IGNITE-13837
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Kalashnikov
> Priority: Major
>
> It needs to think how the first initialization of node/cluster should look
> like. What is the format of initial properties(json/hocon etc.)? How should
> they be handled?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
