Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/21063
I guess we might not even need to make an API change, just document that
these flags only mean anything for microbatch execution. In any case that's a
separate discussion.
---
---
Github user jose-torres commented on the issue:
https://github.com/apache/spark/pull/21063
I'm not sure isDataAvailable makes sense in the context of continuous
processing; it seems fundamentally tied to the microbatch execution model. I
think the best option is to just leave it and i
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 isData
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21063
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/21063
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
