Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
@vanzin
I undertstand the story now, but im afraid i cant help to accomplish that
story.
as my first comment state,
this implementation is base on the current REST implementation of spark-core
and will be available for running applications only
this implementation is mean to fit the current structure,
and the purpose is to retrieve information available from the origin webUI
as json string
what you trying to accomplish is more like to implement a version 2 api
that will be out of both my scope and needs
Im not sure but one reason for current streaming webUI does not support
history server can simply because there is no needs.
as a streaming user, I will said a streaming application will never stop
except for maintenance.
thus it is logically meaningless to look into the status of streaming
through history server.
I still believe my current implementation is good enough for the current
structure.
and will benefit some user out there
If somehow people understand streaming like @tdas or @srowen agree with me
I think we can still merge this implement as version 1 api
otherwise, i will close this PR and let your guys work on it.
and hopefully we will have a streaming api soon.
---
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]
