Hi Junkai,
Thanks a lot. I'll try with expiry time then. Is this[1] the place where
Helix has implemented this logic? If that so, default expiry time should be
24 hours. Am I right?
[1]
https://github.com/apache/helix/blob/master/helix-core/src/main/java/org/apache/helix/task/TaskUtil.java#L711
The Apache Jenkins build system has built helix (build #1571)
Status: Still Failing
Check console output at https://builds.apache.org/job/helix/1571/ to view the
results.
Yes. You are right.
On Tue, Nov 13, 2018 at 7:32 AM DImuthu Upeksha
wrote:
> Hi Junkai,
>
> Thanks a lot. I'll try with expiry time then. Is this[1] the place where
> Helix has implemented this logic? If that so, default expiry time should be
> 24 hours. Am I right?
>
> [1]
>
> https://github.co
The Apache Jenkins build system has built helix (build #1572)
Status: Still Failing
Check console output at https://builds.apache.org/job/helix/1572/ to view the
results.
Hunter L created HELIX-789:
--
Summary: REST2.0: Add support for update and delete for
ResourceConfig
Key: HELIX-789
URL: https://issues.apache.org/jira/browse/HELIX-789
Project: Apache Helix
Issue T
Hunter L created HELIX-790:
--
Summary: REST2.0: Add support for updating IdealState
Key: HELIX-790
URL: https://issues.apache.org/jira/browse/HELIX-790
Project: Apache Helix
Issue Type: Improvement
GitHub user narendly opened a pull request:
https://github.com/apache/helix/pull/295
PR
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/narendly/helix master
Alternatively you can review and apply these changes as the patch at: