Github user tdas commented on the issue:

    https://github.com/apache/spark/pull/15497
  
    I thought about it, and I still dont like this design. This is adding more 
complexity in a general class ManualClock, for functionality needed only by 
StreamExecution. And that leads to these sort of question - should the general 
feature like `isThreadWaiting` work with multiple threads, etc. 
    
    I think we need to do it differently. I think its best to create a custom 
ManualClock for StreamExecution, which adds the functionality necessary for 
StreamExecution.
    
    Mind if I take over this PR and work this out (in the interest of time, 
2.0.2 cutoff is imminent)?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to