Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Thu, 19 Feb 2015 20:33:11 +0000 (UTC)
From: "Tom Byrne (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12776271.1424377950000.89274.1424377991506@Atlassian.JIRA>
In-Reply-To: <JIRA.12776271.1424377950000@Atlassian.JIRA>
References: <JIRA.12776271.1424377950000@Atlassian.JIRA>
 <JIRA.12776271.1424377950935@arcas>
Subject: [jira] [Created] (CURATOR-189) Inconsistent path validation for
 creatingParentsIfNeeded().withMode(CreateMode.PERSISTENT_SEQUENTIAL)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Tom Byrne created CURATOR-189:
---------------------------------

             Summary: Inconsistent path validation for creatingParentsIfNeeded().withMode(CreateMode.PERSISTENT_SEQUENTIAL)
                 Key: CURATOR-189
                 URL: https://issues.apache.org/jira/browse/CURATOR-189
             Project: Apache Curator
          Issue Type: Bug
          Components: Framework
    Affects Versions: 2.4.2
         Environment: MacOSX
            Reporter: Tom Byrne
            Priority: Minor


There is an inconsistency in handling paths when calling:

curator.create().creatingParentsIfNeeded().withMode(CreateMode.PERSISTENT_SEQUENTIAL).forPath(). If the path passed ends with a "/", the call will succeed if the parents exist, but fail if it does not exist. 

There is no path validation done on the parent path unless it needs to be created. 

I think the correct behavior should be that if the parent path ends with a "/", then just to remove the slash and create the parents anyways. 


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