[GitHub] [helix] narendly commented on issue #357: [WIP] Add getWorkflows(long timeout) to TaskDriver.

[GitBox <gi...@apache.org>]

narendly commented on issue #357: [WIP] Add getWorkflows(long timeout) to TaskDriver.
URL: https://github.com/apache/helix/pull/357#issuecomment-514101832
 
 
   Please review the pull request guidelines and format your pull request accordingly.
   
   On Jul 23, 2019, 10:01, at 10:01, pkuwm <no...@github.com> wrote:
   >Sometimes zookeeper hangs in the getWorkflows() call, and we could
   >provide an API with a timeout to handle this at the application level.
   >Use ExcecutorService and Future to implement the timeout function.
   >Call future.get(long timeout, TimeUnit timeUnit) to wait for result.
   >
   >This commit resolves #326:
   >1. Add a static API parseWorkflowConfig to class WorkflowConfig.
   >The API can parse HelixProperty.
   >2. Add an API getWorkflows(long timeout) to TaskDriver.
   >You can view, comment on, or merge this pull request online at:
   >
   >  https://github.com/apache/helix/pull/357
   >
   >-- Commit Summary --
   >
   >  * Add getWorkflows(long timeout) to TaskDriver.
   >
   >-- File Changes --
   >
   >  M helix-core/src/main/java/org/apache/helix/task/TaskDriver.java (54)
   >M helix-core/src/main/java/org/apache/helix/task/WorkflowConfig.java
   >(16)
   >
   >-- Patch Links --
   >
   >https://github.com/apache/helix/pull/357.patch
   >https://github.com/apache/helix/pull/357.diff
   >
   >-- 
   >You are receiving this because you are subscribed to this thread.
   >Reply to this email directly or view it on GitHub:
   >https://github.com/apache/helix/pull/357
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services