[ 
https://issues.apache.org/jira/browse/CURATOR-590?focusedWorklogId=561798&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-561798
 ]

ASF GitHub Bot logged work on CURATOR-590:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Mar/21 15:51
            Start Date: 06/Mar/21 15:51
    Worklog Time Spent: 10m 
      Work Description: pboutes opened a new pull request #380:
URL: https://github.com/apache/curator/pull/380


   Adds a `useParentCreation` boolean flag to control the parent creation.
   
   If this flag is set to `false`, the `PersistentNode` won't create the 
underlying znodes with the `createParentContainersIfNeeded()`, meaning that the 
parent znodes will have to exist beforehand in order for the `PersistentNode` 
to succeed its creation.
   
   The `useParentCreation` flag is set to `true` by default.
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 561798)
    Remaining Estimate: 0h
            Time Spent: 10m

> Adds possibility to disable parent creation for PersistentNode
> --------------------------------------------------------------
>
>                 Key: CURATOR-590
>                 URL: https://issues.apache.org/jira/browse/CURATOR-590
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Recipes
>    Affects Versions: 4.3.0
>            Reporter: Boutes Paul
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should be able to add an option to the PersistentNode in order to turn 
> parent creation off.
> For example:
> given this znode path containing some data:
> {noformat}
> /one/two{noformat}
>  and a PersistentNode under
> {code:java}
> /one/two/three{code}
> If the former path is deleted (with deleting children if needed),
> the PersistentNode will recreate the full hierarchy but with empty data for
> {code:java}
> /one/two{code}
> That can be misleading for external process looking at these paths, thinking 
> that something is up (wrongfully).
> The idea is to add a boolean flag to the PersistentNode recipe to disable the 
> parent creation when creating / recreating znode in order to avoid such 
> situation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to