curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Henke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-278) In transactions compressed option does not work with some fluent api combinations
Date Thu, 12 Nov 2015 22:56:11 GMT

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

Grant Henke commented on CURATOR-278:
-------------------------------------

[~mdrob] This is meant to be a small, quick fix change to support my libraries needs. I am
not sure how that compares or contrasts to CURATOR-148, but that jira seams like it has a
larger goal. Currently all of the fluent apis require some specific ordering and I agree the
ordering and type passing in the interfaces is complicated and error prone (caused this jira).
Removing that requirement or potentially making it optional would be great.


> In transactions compressed option does not work with some fluent api combinations
> ---------------------------------------------------------------------------------
>
>                 Key: CURATOR-278
>                 URL: https://issues.apache.org/jira/browse/CURATOR-278
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.9.1
>            Reporter: Grant Henke
>            Assignee: Mike Drob
>
> I can't find a way to use compression with the following options in transactions. These
do not compile:
> - _transaction.setData().compressed().withVersion(1).forPath("/path")_
> -  _transaction.create().compressed().withMode(CreateMode.PERSISTENT).forPath("path")_
 
> - _transaction.create().compressed().withMode(CreateMode.PERSISTENT).withACL(ZooDefs.Ids.OPEN_ACL_UNSAFE).forPath("path")_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message