Hexiaoqiao commented on PR #478: URL: https://github.com/apache/curator/pull/478#issuecomment-1718708611
> The later behavior is a bug due to the contract what trySetCount try to express. As a library, I don't think Curator should do that for callers silently. +1, Agree. So how about expose the choice to end user and offer some configuration items to set? IMO, some sensitive data should not be updated blindly, but some case we should offer solution to bypass this bug, such as `Token for Hadoop` as mentioned above, which can update smoothly even blindly. What do you think about? TBH, I am not familiar with implement about Curator, so would you mind to list some demo code snippet about configuration if this solution could be approved. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
