[jira] [Commented] (CURATOR-477) Ability to turn off Zk Watches in Curator Framework

[ https://issues.apache.org/jira/browse/CURATOR-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624965#comment-16624965 ] Scott Blum commented on CURATOR-477: PR seems fine to me if that's what we want, although I wonder

[jira] [Comment Edited] (CURATOR-477) Ability to turn off Zk Watches in Curator Framework

[ https://issues.apache.org/jira/browse/CURATOR-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16624965#comment-16624965 ] Scott Blum edited comment on CURATOR-477 at 9/23/18 4:52 AM: - PR seems fine

[jira] [Comment Edited] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993647#comment-15993647 ] Scott Blum edited comment on CURATOR-406 at 5/2/17 8:15 PM: What I did.

[jira] [Commented] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993647#comment-15993647 ] Scott Blum commented on CURATOR-406: What I did. (Note, my Apache remote is named "apache" in my

[jira] [Comment Edited] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993647#comment-15993647 ] Scott Blum edited comment on CURATOR-406 at 5/2/17 8:14 PM: What I did.

[jira] [Commented] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993637#comment-15993637 ] Scott Blum commented on CURATOR-406: I'm not super strongly opinionated, but I haven't seen other

[jira] [Resolved] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-406. Resolution: Fixed - master is on 3.0 now - I left a CURATOR-2.0 branch where master was, you

[jira] [Comment Edited] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993606#comment-15993606 ] Scott Blum edited comment on CURATOR-406 at 5/2/17 7:55 PM: Do you want the

[jira] [Comment Edited] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993606#comment-15993606 ] Scott Blum edited comment on CURATOR-406 at 5/2/17 7:55 PM: Do you want the

[jira] [Comment Edited] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993606#comment-15993606 ] Scott Blum edited comment on CURATOR-406 at 5/2/17 7:56 PM: Do you want the

[jira] [Assigned] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-406: -- Assignee: Scott Blum > The CURATOR-3.0 branch should become master >

[jira] [Commented] (CURATOR-406) The CURATOR-3.0 branch should become master

[ https://issues.apache.org/jira/browse/CURATOR-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15993606#comment-15993606 ] Scott Blum commented on CURATOR-406: Do you want the old master as "master-2.0" or "CURATOR-2.0" to

[jira] [Commented] (CURATOR-171) LeaderLatch isn't aware if it's own ephemeral node goes away

[ https://issues.apache.org/jira/browse/CURATOR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826685#comment-15826685 ] Scott Blum commented on CURATOR-171: I think he's saying, the leader can talk to ZK (no partition

[jira] [Commented] (CURATOR-171) LeaderLatch isn't aware if it's own ephemeral node goes away

[ https://issues.apache.org/jira/browse/CURATOR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824551#comment-15824551 ] Scott Blum commented on CURATOR-171: I could totally get on board with the idea that everyone watches

[jira] [Commented] (CURATOR-171) LeaderLatch isn't aware if it's own ephemeral node goes away

[ https://issues.apache.org/jira/browse/CURATOR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822946#comment-15822946 ] Scott Blum commented on CURATOR-171: For what it's worth (this isn't a Curator issue), but in Solr

[jira] [Assigned] (CURATOR-374) Reduce memory usage in TreeCache

[ https://issues.apache.org/jira/browse/CURATOR-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-374: -- Assignee: Scott Blum > Reduce memory usage in TreeCache > >

[jira] [Commented] (CURATOR-319) NodeCache recreates deleted parents of the node being cached

[ https://issues.apache.org/jira/browse/CURATOR-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267204#comment-15267204 ] Scott Blum commented on CURATOR-319: I understand in the past there may have been an issue with

[jira] [Commented] (CURATOR-319) NodeCache recreates deleted parents of the node being cached

[ https://issues.apache.org/jira/browse/CURATOR-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267181#comment-15267181 ] Scott Blum commented on CURATOR-319: I actually have to agree with Tommy in principle. It makes

[jira] [Commented] (CURATOR-319) NodeCache recreates deleted parents of the node being cached

[ https://issues.apache.org/jira/browse/CURATOR-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15267103#comment-15267103 ] Scott Blum commented on CURATOR-319: As a workaround, if you use TreeCache with depth = 0 it won't

[jira] [Commented] (CURATOR-288) Provide a mechanism to limit tree traversal in TreeCache + Return old values in NODE_REMOVED event

[ https://issues.apache.org/jira/browse/CURATOR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15159447#comment-15159447 ] Scott Blum commented on CURATOR-288: Isn't this done now, with TreeCacheSelector? > Provide a

[jira] [Resolved] (CURATOR-302) TestTreeCache.testKilledSession() fails in 3.0 branch

[ https://issues.apache.org/jira/browse/CURATOR-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-302. Resolution: Fixed > TestTreeCache.testKilledSession() fails in 3.0 branch >

[jira] [Created] (CURATOR-302) TestTreeCache.testKilledSession() fails in 3.0 branch

Scott Blum created CURATOR-302: -- Summary: TestTreeCache.testKilledSession() fails in 3.0 branch Key: CURATOR-302 URL: https://issues.apache.org/jira/browse/CURATOR-302 Project: Apache Curator

[jira] [Commented] (CURATOR-296) Notify cache listeners when re-init completes after reconnect

[ https://issues.apache.org/jira/browse/CURATOR-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126850#comment-15126850 ] Scott Blum commented on CURATOR-296: [~cammckenzie] gave me an LGTM so I went ahead and merged what I

[jira] [Resolved] (CURATOR-296) Notify cache listeners when re-init completes after reconnect

[ https://issues.apache.org/jira/browse/CURATOR-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-296. Resolution: Fixed Fix Version/s: 2.9.2 3.0.1 > Notify cache listeners

[jira] [Assigned] (CURATOR-296) Notify cache listeners when re-init completes after reconnect

[ https://issues.apache.org/jira/browse/CURATOR-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-296: -- Assignee: Scott Blum > Notify cache listeners when re-init completes after reconnect >

[jira] [Resolved] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-294. Resolution: Fixed > Optimize TreeCache, fix possible concurrency issue >

[jira] [Commented] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124698#comment-15124698 ] Scott Blum commented on CURATOR-294: Re-spun the PR per [~nickhill] suggestions. > Optimize

[jira] [Commented] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123940#comment-15123940 ] Scott Blum commented on CURATOR-294: Great idea! > Optimize TreeCache, fix possible concurrency

[jira] [Created] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

Scott Blum created CURATOR-294: -- Summary: Optimize TreeCache, fix possible concurrency issue Key: CURATOR-294 URL: https://issues.apache.org/jira/browse/CURATOR-294 Project: Apache Curator

[jira] [Commented] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121851#comment-15121851 ] Scott Blum commented on CURATOR-294: Nick, Looking at this closer, I see your point! There is a

[jira] [Commented] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121849#comment-15121849 ] Scott Blum commented on CURATOR-294: It just seems that not guaranteeing consistency of the stat and

[jira] [Comment Edited] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122155#comment-15122155 ] Scott Blum edited comment on CURATOR-294 at 1/28/16 7:28 PM: - [~randgalt] or

[jira] [Commented] (CURATOR-294) Optimize TreeCache, fix possible concurrency issue

[ https://issues.apache.org/jira/browse/CURATOR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122155#comment-15122155 ] Scott Blum commented on CURATOR-294: [~randgalt] I pushed a branch, would you mind reviewing? Or

[jira] [Commented] (CURATOR-256) Provide curator artifact in Maven Central with Guava shaded away

[ https://issues.apache.org/jira/browse/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725495#comment-14725495 ] Scott Blum commented on CURATOR-256: Later releases of Guava are largely backwards compatible with

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710132#comment-14710132 ] Scott Blum commented on CURATOR-167: Sorry for being dumb, can someone give me the

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710231#comment-14710231 ] Scott Blum commented on CURATOR-167: Nevermind, just saw your branch. Cool! All

[jira] [Assigned] (CURATOR-240) Severe memory leak in TreeCache when path does not exist

[ https://issues.apache.org/jira/browse/CURATOR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-240: -- Assignee: Scott Blum Severe memory leak in TreeCache when path does not exist

[jira] [Comment Edited] (CURATOR-236) TreeCache throws IllegalArgumentException when node is a substring of the requested path

[ https://issues.apache.org/jira/browse/CURATOR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630408#comment-14630408 ] Scott Blum edited comment on CURATOR-236 at 7/16/15 9:56 PM: -

[jira] [Commented] (CURATOR-236) TreeCache throws IllegalArgumentException when node is a substring of the requested path

[ https://issues.apache.org/jira/browse/CURATOR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630208#comment-14630208 ] Scott Blum commented on CURATOR-236: Good catch, I'll take a look TreeCache throws

[jira] [Comment Edited] (CURATOR-236) TreeCache throws IllegalArgumentException when node is a substring of the requested path

[ https://issues.apache.org/jira/browse/CURATOR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630408#comment-14630408 ] Scott Blum edited comment on CURATOR-236 at 7/16/15 9:57 PM: -

[jira] [Work started] (CURATOR-236) TreeCache throws IllegalArgumentException when node is a substring of the requested path

[ https://issues.apache.org/jira/browse/CURATOR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-236 started by Scott Blum. -- TreeCache throws IllegalArgumentException when node is a substring of the

[jira] [Updated] (CURATOR-218) Race condition in client.blockUntilConnected()

[ https://issues.apache.org/jira/browse/CURATOR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated CURATOR-218: --- Summary: Race condition in client.blockUntilConnected() (was: TreeCache initialization problem with

[jira] [Commented] (CURATOR-218) TreeCache initialization problem with non existant root path

[ https://issues.apache.org/jira/browse/CURATOR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618879#comment-14618879 ] Scott Blum commented on CURATOR-218: Very cool. Seems like I should reassign this

[jira] [Closed] (CURATOR-145) TreeCache should implement maxDepth

[ https://issues.apache.org/jira/browse/CURATOR-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum closed CURATOR-145. -- TreeCache should implement maxDepth --- Key:

[jira] [Commented] (CURATOR-218) TreeCache initialization problem with non existant root path

[ https://issues.apache.org/jira/browse/CURATOR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14540899#comment-14540899 ] Scott Blum commented on CURATOR-218: I can't repro this on master, I've run it

[jira] [Commented] (CURATOR-173) InterProcessSemaphoreV2 nodes not reapable

[ https://issues.apache.org/jira/browse/CURATOR-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389937#comment-14389937 ] Scott Blum commented on CURATOR-173: I think so, I merged the PR.

[jira] [Resolved] (CURATOR-182) TreeCache breaks when root node is removed

[ https://issues.apache.org/jira/browse/CURATOR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-182. Resolution: Fixed TreeCache breaks when root node is removed

[jira] [Reopened] (CURATOR-182) TreeCache breaks when root node is removed

[ https://issues.apache.org/jira/browse/CURATOR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reopened CURATOR-182: TreeCache breaks when root node is removed --

[jira] [Updated] (CURATOR-183) TreeCache not properly handling repeated add/removal of root node

[ https://issues.apache.org/jira/browse/CURATOR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated CURATOR-183: --- Affects Version/s: 2.7.0 2.7.1 Fix Version/s: (was: 2.7.0)

[jira] [Resolved] (CURATOR-182) TreeCache breaks when root node is removed

[ https://issues.apache.org/jira/browse/CURATOR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-182. Resolution: Duplicate TreeCache breaks when root node is removed

[jira] [Resolved] (CURATOR-183) TreeCache not properly handling repeated add/removal of root node

[ https://issues.apache.org/jira/browse/CURATOR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-183. Resolution: Fixed TreeCache not properly handling repeated add/removal of root node

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268850#comment-14268850 ] Scott Blum commented on CURATOR-179: [~cammckenzie] i pushed a commit on your branch,

[jira] [Commented] (CURATOR-179) Sequential path creation of /somepath/N throws exception

[ https://issues.apache.org/jira/browse/CURATOR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14268486#comment-14268486 ] Scott Blum commented on CURATOR-179: I think what would be useful is a test case

[jira] [Assigned] (CURATOR-178) Pull request: Use Curator in thread names

[ https://issues.apache.org/jira/browse/CURATOR-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-178: -- Assignee: Scott Blum Pull request: Use Curator in thread names

[jira] [Assigned] (CURATOR-177) Pull request: Use Curator in thread names

[ https://issues.apache.org/jira/browse/CURATOR-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-177: -- Assignee: Scott Blum Pull request: Use Curator in thread names

[jira] [Assigned] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-167: -- Assignee: Scott Blum Memory leak in NodeCache

[jira] [Commented] (CURATOR-167) Memory leak in NodeCache

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216364#comment-14216364 ] Scott Blum commented on CURATOR-167: Thanks for the report! Do you have / are you

[jira] [Assigned] (CURATOR-144) TreeCache should use a builder for advanced options

[ https://issues.apache.org/jira/browse/CURATOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum reassigned CURATOR-144: -- Assignee: Scott Blum TreeCache should use a builder for advanced options

[jira] [Commented] (CURATOR-136) Invalid LeaderLatch path never errors

[ https://issues.apache.org/jira/browse/CURATOR-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14197632#comment-14197632 ] Scott Blum commented on CURATOR-136: Should we rename the title of this jira? I just

[jira] [Updated] (CURATOR-143) Introduce a max depth setting for TreeCache

[ https://issues.apache.org/jira/browse/CURATOR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated CURATOR-143: --- Fix Version/s: (was: 2.7.0) 2.7.1 Introduce a max depth setting for

[jira] [Resolved] (CURATOR-143) Introduce a max depth setting for TreeCache

[ https://issues.apache.org/jira/browse/CURATOR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum resolved CURATOR-143. Resolution: Fixed Fixed and released max depth support; please enter a separate JIRA for

[jira] [Updated] (CURATOR-143) Introduce a max depth setting for TreeCache

[ https://issues.apache.org/jira/browse/CURATOR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated CURATOR-143: --- Fix Version/s: (was: 2.7.1) 2.7.0 Introduce a max depth setting for

[jira] [Closed] (CURATOR-151) SharedValue has limited utility but can be improved

[ https://issues.apache.org/jira/browse/CURATOR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum closed CURATOR-151. -- SharedValue has limited utility but can be improved ---

[jira] [Commented] (CURATOR-135) API Cleanup: Avoid throwing Exception

[ https://issues.apache.org/jira/browse/CURATOR-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14165442#comment-14165442 ] Scott Blum commented on CURATOR-135: I see both sides of it, but personally I tend to

[jira] [Commented] (CURATOR-151) SharedValue has limited utility but can be improved

[ https://issues.apache.org/jira/browse/CURATOR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157051#comment-14157051 ] Scott Blum commented on CURATOR-151: I can't find the pull request. How do I comment

[jira] [Commented] (CURATOR-151) SharedValue has limited utility but can be improved

[ https://issues.apache.org/jira/browse/CURATOR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157063#comment-14157063 ] Scott Blum commented on CURATOR-151: Thanks, much better! I did have one gut

[jira] [Commented] (CURATOR-151) SharedValue has limited utility but can be improved

[ https://issues.apache.org/jira/browse/CURATOR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14157075#comment-14157075 ] Scott Blum commented on CURATOR-151: Yeah, I considered that, but have a mild

[jira] [Created] (CURATOR-144) TreeCache should use a builder for advanced options

Scott Blum created CURATOR-144: -- Summary: TreeCache should use a builder for advanced options Key: CURATOR-144 URL: https://issues.apache.org/jira/browse/CURATOR-144 Project: Apache Curator

[jira] [Commented] (CURATOR-138) Unify event listening for NodeCache, PathChildrenCache, TreeCache

[ https://issues.apache.org/jira/browse/CURATOR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104682#comment-14104682 ] Scott Blum commented on CURATOR-138: I don't believe there's a ticket filed yet.

[jira] [Created] (CURATOR-138) Unify event listening for NodeCache, PathChildrenCache, TreeCache

Scott Blum created CURATOR-138: -- Summary: Unify event listening for NodeCache, PathChildrenCache, TreeCache Key: CURATOR-138 URL: https://issues.apache.org/jira/browse/CURATOR-138 Project: Apache

[jira] [Commented] (CURATOR-128) There is no namespace-safe way to refer to the root node

[ https://issues.apache.org/jira/browse/CURATOR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077855#comment-14077855 ] Scott Blum commented on CURATOR-128: Sure let me give a very concrete problem this is

[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close

[ https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076457#comment-14076457 ] Scott Blum commented on CURATOR-126: Also, versions of Java 1.8 have a bug in

[jira] [Commented] (CURATOR-125) ConnectionStateListener is confused by READ_ONLY state

[ https://issues.apache.org/jira/browse/CURATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076573#comment-14076573 ] Scott Blum commented on CURATOR-125: Please delete the above 3 comments (and this

[jira] [Commented] (CURATOR-126) IllegalStateException in performBackgroundOperation during close

[ https://issues.apache.org/jira/browse/CURATOR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14076576#comment-14076576 ] Scott Blum commented on CURATOR-126: You're right, Thread.interrupt(), Thread.join()

[jira] [Created] (CURATOR-128) There is no namespace-safe way to refer to the root node

Scott Blum created CURATOR-128: -- Summary: There is no namespace-safe way to refer to the root node Key: CURATOR-128 URL: https://issues.apache.org/jira/browse/CURATOR-128 Project: Apache Curator

[jira] [Commented] (CURATOR-128) There is no namespace-safe way to refer to the root node

[ https://issues.apache.org/jira/browse/CURATOR-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077388#comment-14077388 ] Scott Blum commented on CURATOR-128: It couldn't be made more lenient? e.g. / +

[jira] [Updated] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Blum updated CURATOR-33: -- Attachment: CURATOR-33.2.patch Rebased patch, removed extraneous format changes. Recursive Node

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14056926#comment-14056926 ] Scott Blum commented on CURATOR-33: --- I think a pretty significant amount of rework would

[jira] [Commented] (CURATOR-33) Recursive Node Cache

[ https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14057033#comment-14057033 ] Scott Blum commented on CURATOR-33: --- Thanks, I do see some things in there that look