Github user jose-torres commented on the issue:
    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 isTriggerActive always false, and 
take a TODO to restructure StreamingQueryStatus to eliminate the assumption 
they're meaningful. (The latter would be an API change, so we'd definitely want 
a separate PR for it - fortunately StreamingQueryStatus isn't stable yet.)


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to