Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AA7E418CA5 for ; Wed, 1 Jul 2015 21:15:04 +0000 (UTC) Received: (qmail 21560 invoked by uid 500); 1 Jul 2015 21:15:04 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 21508 invoked by uid 500); 1 Jul 2015 21:15:04 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 21494 invoked by uid 99); 1 Jul 2015 21:15:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 21:15:04 +0000 Date: Wed, 1 Jul 2015 21:15:04 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-222) Support Container Nodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-222?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D146= 11007#comment-14611007 ]=20 ASF GitHub Bot commented on CURATOR-222: ---------------------------------------- Github user Randgalt commented on the pull request: https://github.com/apache/curator/pull/79#issuecomment-117826258 =20 > Can the internal EnsurePath stuff in NamespaceImpl be replaced with t= he new container stuff? =20 Possibly, but I'm deprecating EnsurePath so I don't see the need to add= to it =20 > When executing creatingContainerParentsIfNeeded(), I was wondering if= some sort of warning log should be generated if the parents already exist = and are not container nodes?=20 =20 Unfortunately, there's no way to know if a node is a container or not r= ight now. I had to shoehorn container support in with a hack. Maybe in a fu= ture version of ZK. > Support Container Nodes > ----------------------- > > Key: CURATOR-222 > URL: https://issues.apache.org/jira/browse/CURATOR-222 > Project: Apache Curator > Issue Type: New Feature > Components: Client, Framework, Recipes > Affects Versions: 2.8.0 > Reporter: Jordan Zimmerman > Assignee: Jordan Zimmerman > Fix For: 2.9.0 > > > ZooKeeper will most likely add support for "Container" nodes per https://= issues.apache.org/jira/browse/ZOOKEEPER-2163 - Curator must support this fe= ature > * Backwards compatible to 3.4.6. If Containers are available, they=E2=80= =99re used in all recipes that create parent nodes. > * The use of EnsurePath is now deprecated -- This message was sent by Atlassian JIRA (v6.3.4#6332)