You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@helix.apache.org by GitBox <gi...@apache.org> on 2019/07/21 08:32:59 UTC

[GitHub] [helix] narendly commented on issue #326: Add getWorkflow(long timeout) to TaskDriver

narendly commented on issue #326: Add getWorkflow(long timeout) to TaskDriver
URL: https://github.com/apache/helix/issues/326#issuecomment-513534644
 
 
   It is a typo - it is getWorkflows(). For now, only adding getWorkflows (timeout) would suffice.
   
   Hunter
   
   ⁣Sent from BlueMail 
   
   On Jul 21, 2019, 09:58, at 09:58, pkuwm <no...@github.com> wrote:
   >I don't see the call: getWorkflow() in the source code. Did you mean
   >[getWorkflows](https://github.com/apache/helix/blob/3e670ded2ece50e21b76fcab7fed7cb61a24eea1/helix-core/src/main/java/org/apache/helix/task/TaskDriver.java#L836)()?
   >
   >  public Map<String, WorkflowConfig> getWorkflows() 
   >
   >Do you think it is alright to have a default timeout for the current
   >call getWorkflows() and also add a new api getWorkflow(long timeout) ?
   >
   >-- 
   >You are receiving this because you authored the thread.
   >Reply to this email directly or view it on GitHub:
   >https://github.com/apache/helix/issues/326#issuecomment-513532438
   

----------------------------------------------------------------
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