You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Mridul Verma (JIRA)" <ji...@apache.org> on 2016/12/31 08:01:58 UTC

[jira] [Updated] (CURATOR-372) CompressionProvider should not take path as an Arguement

     [ https://issues.apache.org/jira/browse/CURATOR-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Verma updated CURATOR-372:
---------------------------------
    Summary: CompressionProvider should not take path as an Arguement  (was: CompressionProvider Function Signatures should not include the path)

> CompressionProvider should not take path as an Arguement
> --------------------------------------------------------
>
>                 Key: CURATOR-372
>                 URL: https://issues.apache.org/jira/browse/CURATOR-372
>             Project: Apache Curator
>          Issue Type: Task
>          Components: Framework
>            Reporter: Mridul Verma
>            Priority: Trivial
>
> Currently in Curator-Framework in Compression Provider, we 
> {code}
> compress(String path, byte[] data)
> {code}
> we use the path, but the `path` is not required for this functionality.
> So we should clean this up.



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