[
https://issues.apache.org/jira/browse/HELIX-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106258#comment-14106258
]
Hudson commented on HELIX-329:
--
UNSTABLE: Integrated in helix #1285 (See
[https://builds.apac
The Apache Jenkins build system has built helix (build #1285)
Status: Still Unstable
Check console output at https://builds.apache.org/job/helix/1285/ to view the
results.
It's been quite some time and we've made many changes since the last Helix
release. Here is what we could provide with each release:
0.6.4- Bug fixes- Task framework- New metrics
0.7.1 (beta)- Performance improvements- API simplification- Task framework-
YARN support- IPC
Any thoughts? Is there a
Kanak Biscuitwala created HELIX-505:
---
Summary: Prevent creation of resource names with pipe character
Key: HELIX-505
URL: https://issues.apache.org/jira/browse/HELIX-505
Project: Apache Helix
Yes, that would probably be best. I think what Greg has is a reasonable v1 for
helix-ipc, and (feel free to disagree with me) should be flexible enough as a
base for most future things we want to build, including multi-ZK support.
Kanak
Date: Thu, 21 Aug 2014 14:07:35 -0700
Subject: Re: Add perf
Should we move the ZK cross data center to a separate thread. This is an
interesting problem and probably needs more detailed discussions.
What do you guys think.
On Wed, Aug 20, 2014 at 7:44 PM, Kanak Biscuitwala
wrote:
> Hey Vlad,
>
> In theory, we should be able to plug in a resolver that c
Kanak Biscuitwala created HELIX-504:
---
Summary: Controller should avoid resetting watches on removed paths
Key: HELIX-504
URL: https://issues.apache.org/jira/browse/HELIX-504
Project: Apache Helix
