> 3. triggerExecution is effectively end-to-end processing time for the
>>> micro-batch, note all other durations sum closely to triggerExecution,
>>> there
>>> is a little slippage based on book-keeping activities in StreamExecution.
>>>
>>
&
e the DataFrame.
>
>
>> 3. triggerExecution is effectively end-to-end processing time for the
>> micro-batch, note all other durations sum closely to triggerExecution,
>> there
>> is a little slippage based on book-keeping activities in StreamExecution.
>>
>
re
> is a little slippage based on book-keeping activities in StreamExecution.
>
Yes. Precisely.
>
>
>
> --
> View this message in context: http://apache-spark-user-list.
> 1001560.n3.nabble.com/Structured-Streaming-multiple-
> sinks-tp29056p29105.html
> Se
processing time for the
micro-batch, note all other durations sum closely to triggerExecution, there
is a little slippage based on book-keeping activities in StreamExecution.
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Structured-Streaming-multiple-sinks
ionMs" : {
"addBatch" : 2263426,
"getBatch" : 12,
"getOffset" : 273,
"queryPlanning" : 13,
"triggerExecution" : 2264288,
"walCommit" : 552
},
regards
aravias
--
View this message in context:
http://apache-spark-user-list.