[
https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1400#comment-1400
]
Cameron McKenzie commented on CURATOR-79:
-
If you run this test twice, won't the
[
https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14088915#comment-14088915
]
Cameron McKenzie commented on CURATOR-79:
-
I've made some changes to the unit test
[
https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14088920#comment-14088920
]
Orcun Simsek commented on CURATOR-79:
-
Thanks a lot for looking into it and I'm glad
Curator already has the EnsembleProvider interface that I wrote to integrate
with Exhibitor. We might be able to repurpose it for this.
-JZ
From: Cameron McKenzie mckenzie@gmail.com
Reply: dev@curator.apache.org dev@curator.apache.org
Date: August 7, 2014 at 12:45:21 AM
To:
I think we should list all the changes that we need to do and get Jira’s
written for them (targeted for version 3.0.0) and then we can divide up the
work.
-JZ
From: Cameron McKenzie mckenzie@gmail.com
Reply: dev@curator.apache.org dev@curator.apache.org
Date: August 7, 2014 at 12:45:21 AM
I saw that they added the ability to remove watches, so that could be a
viable approach for CURATOR-14?
Are we using a JIRA label to group the issues and make them easily findable?
Mike
On Thu, Aug 7, 2014 at 9:54 AM, Jordan Zimmerman jor...@jordanzimmerman.com
wrote:
I think we should list
We could use a label. However, I have version 3.0.0 set for ZK 3.5.x
compatibility so we can just use that.
-JZ
From: Mike Drob mad...@cloudera.com
Reply: dev@curator.apache.org dev@curator.apache.org
Date: August 7, 2014 at 10:28:16 AM
To: dev@curator.apache.org dev@curator.apache.org
Cc:
Github user dragonsinth commented on a diff in the pull request:
https://github.com/apache/curator/pull/17#discussion_r15959716
--- Diff:
curator-recipes/src/main/java/org/apache/curator/framework/recipes/cache/TreeCache.java
---
@@ -0,0 +1,648 @@
+/**
+ * Licensed to the
[
https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090020#comment-14090020
]
ASF GitHub Bot commented on CURATOR-33:
---
Github user dragonsinth commented on a diff
[
https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090130#comment-14090130
]
ASF GitHub Bot commented on CURATOR-33:
---
Github user cammckenzie commented on a diff
It's good to go from my point of view.
On Fri, Aug 8, 2014 at 12:04 PM, Jordan Zimmerman
jor...@jordanzimmerman.com wrote:
So, where are we with TreeCache (CURATOR-33). Ready for merge?
-Jordan
Github user asfgit closed the pull request at:
https://github.com/apache/curator/pull/17
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/CURATOR-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman resolved CURATOR-33.
-
Resolution: Fixed
Recursive Node Cache
Key:
[
https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090347#comment-14090347
]
Cameron McKenzie commented on CURATOR-79:
-
So, a fix for this is more complicated
14 matches
Mail list logo
