Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
I understand its possible,
and actually I agree having a hooking mechanism is a better approach as
well in turns of programing and if we really need streaming to support history
server.
still, from no hooking mechanism to having hooking mechanism is a change in
structure.
and I cant look at them as they are the same.
the most confusing part for me is does streaming-api belong to streaming
or does it belong to spark-core
from the view of API entry point, it looks it belong to spark-core
but from the program structure view, it definitely belong to streaming
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
