You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/03/12 22:38:43 UTC
[jira] [Resolved] (ZOOKEEPER-1167) C api lacks synchronous version
of sync() call.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michi Mutsuzaki resolved ZOOKEEPER-1167.
----------------------------------------
Resolution: Not A Problem
Sorry for jumping in this late, but this API seems unnecessary based on Ben's comment. I'm closing this. Please reopen it if there is a good use case for this, and then we should add it to both java and c clients.
> C api lacks synchronous version of sync() call.
> -----------------------------------------------
>
> Key: ZOOKEEPER-1167
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1167
> Project: ZooKeeper
> Issue Type: Bug
> Components: c client
> Affects Versions: 3.3.3, 3.4.3, 3.5.0
> Reporter: Nicholas Harteau
> Assignee: Marshall McMullen
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1167.patch
>
>
> Reading through the source, the C API implements zoo_async() which is the zookeeper sync() method implemented in the multithreaded/asynchronous C API. It doesn't implement anything equivalent in the non-multithreaded API.
> I'm not sure if this was oversight or intentional, but it means that the non-multithreaded API can't guarantee consistent client views on critical reads.
> The zkperl bindings depend on the synchronous, non-multithreaded API so also can't call sync() currently.
--
This message was sent by Atlassian JIRA
(v6.2#6252)