[ 
https://issues.apache.org/jira/browse/CURATOR-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765410#comment-17765410
 ] 

Zili Chen edited comment on CURATOR-689 at 9/15/23 1:21 AM:
------------------------------------------------------------

There is a related discussion at CURATOR-542 and I ever implement something 
like a transactional store at https://github.com/apache/flink/pull/9878.


was (Author: tison):
There is a related discussion at 
https://issues.apache.org/jira/browse/CURATOR-542 and I ever implement 
something like a transactional store at 
https://github.com/apache/flink/pull/9878

> Guard create/setData/delete with lock path
> ------------------------------------------
>
>                 Key: CURATOR-689
>                 URL: https://issues.apache.org/jira/browse/CURATOR-689
>             Project: Apache Curator
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: 5.6.0
>            Reporter: Kezhu Wang
>            Priority: Major
>
> Curator has several lock recipes({{LeaderLatch}}, {{InterProcessMutex}} and 
> etc.), but it has no simple intuitive method to guard modification under lock 
> path. I am certain that {{CuratorFramework.transaction}} is capable of this, 
> but I still want a simple way to archive this.
> I implemented one before in 
> [rust|https://docs.rs/zookeeper-client/0.6.1/zookeeper_client/struct.LockClient.html#method.create],
>  but it might be relative hard to it to cooperate well with existing 
> `CreateBuilder`, 'SetDataBuilder` and `DeleteBuilder`.
> It need time to explore, post it here for memories.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to