[
https://issues.apache.org/jira/browse/CURATOR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198971#comment-14198971
]
Paweł Szymczyk commented on CURATOR-163:
I try to deal with it and i prepare pull
[
https://issues.apache.org/jira/browse/CURATOR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198971#comment-14198971
]
Paweł Szymczyk edited comment on CURATOR-163 at 11/5/14 8:03 PM:
--
GitHub user pawelszymczyk opened a pull request:
https://github.com/apache/curator/pull/52
Curator 163 remove node without instances
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pawelszymczyk/curator
CURATOR-163_remove_node_w
[
https://issues.apache.org/jira/browse/CURATOR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198948#comment-14198948
]
Paweł Szymczyk commented on CURATOR-163:
Is Reaper notify ServiceCache that it re
[
https://issues.apache.org/jira/browse/CURATOR-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum resolved CURATOR-144.
Resolution: Fixed
Fix Version/s: 2.7.0
> 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
> -
[
https://issues.apache.org/jira/browse/CURATOR-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198565#comment-14198565
]
Jordan Zimmerman commented on CURATOR-163:
--
The recipe doesn't currently try to
Also, I think we should still make separate branches for each feature but have
a CURATOR-3.0 branch for managing the completed features.
-JZ
On November 5, 2014 at 9:52:16 AM, Ioannis Canellos (ioca...@gmail.com) wrote:
So I picked up CURATOR-160 from the list.
What I have in mind is creati
EnsembleProvider has always been my preference.
On November 5, 2014 at 9:52:16 AM, Ioannis Canellos (ioca...@gmail.com) wrote:
So I picked up CURATOR-160 from the list.
What I have in mind is creating a 3.x branch (as I think that we
generally agree on this) and then add the required DSL on
So I picked up CURATOR-160 from the list.
What I have in mind is creating a 3.x branch (as I think that we
generally agree on this) and then add the required DSL on the curator
framework to support the reconfig and getconfig methods.
As a next step we need to decide how we will handle internally
[
https://issues.apache.org/jira/browse/CURATOR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioannis Canellos reassigned CURATOR-160:
Assignee: Ioannis Canellos (was: Jordan Zimmerman)
> Support Dynamic Reconfig
> -
[
https://issues.apache.org/jira/browse/CURATOR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198043#comment-14198043
]
Ioannis Canellos commented on CURATOR-160:
--
[~randgalt] Are you working on it? o
12 matches
Mail list logo