Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18887
> What is the migration proposal/guides?
Not sure what you mean. There's no change in behavior by default, so
there's no migration of anything needed.
> What should users do when they hit serious bugs that we are unable to
find at this stage?
This is always a question when you introduce a change. This particular
project makes it a bit worse since it's a bigger change. But the answer is the
same: file a bug, we fix it, next release has the fix; if it's really important
for you, you can patch your own Spark, or revert to an older release, as many
people do when they find blockers.
The changes in this project do not influence whether your application will
fail or not; they're isolated to the UI, so at worst it will make things harder
to debug until the issues are fixed.
On the other hand, a lot can be mitigated by testing; there's already a lot
of test coverage for parts of this code, but the UI is kinda the exception
there. So the longer these changes stay in review instead of being committed,
the less coverage they'll have in people's day to day testing, actually
increasing the risk that some bug might be missed.
> What are the external behavior changes between the new and the old ones?
None by default.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
