Github user efimpoberezkin commented on the issue:

    https://github.com/apache/spark/pull/21063
  
    @jose-torres Hi Jose, I've added a couple of update messages to places you 
suggested, query stop indeed seems to be reported in StreamExecution.
    I have a question regarding updating isDataAvailable field of query status. 
In MicroBatchExecution it is updated based on the result of comparison of 
committed and available offsets, and the latter is being changed in 
constructNextBatch(). Would the same approach be valid for ContinuousExecuction 
and if yes how should available offsets be updated?


---

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

Reply via email to