Github user boy-uber commented on the issue:
https://github.com/apache/spark/pull/22429
> @boy-uber, for structured streaming, let's do it out of this PR. I think
the actual change of this PR can be small (1.). We can change this API for
structured streaming later if need
Github user boy-uber commented on the issue:
https://github.com/apache/spark/pull/22429
> > @MaxGekk I sent email to spark dev list about structured plan logging,
but did not get any response.
>
> @boy-uber I guess It is better to speak about the feature t
Github user boy-uber commented on the issue:
https://github.com/apache/spark/pull/22429
> > @boy-uber the thing you are suggesting is a pretty big undertaking and
beyond the scope of this PR.
> > If you are going to add structured plans to the explain output, you
p
Github user boy-uber commented on the issue:
https://github.com/apache/spark/pull/22429
> @boy-uber the thing you are suggesting is a pretty big undertaking and
beyond the scope of this PR.
>
> If you are going to add structured plans to the explain output, you
prob
Github user boy-uber commented on the issue:
https://github.com/apache/spark/pull/22429
Great to see the code here to capture more information from the plan and
save to file. We have similar needs with our Spark applications as well.
Adding my two cents:
1. Anyone
Github user boy-uber commented on the pull request:
https://github.com/apache/spark/pull/2633#issuecomment-214151289
Now Spark has improved a lot in fault-tolerance, robustness, and stability.
Could we revisit this PR?
There is a lot of value supporting event timestamp, since
