Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
I could not agree with "The API should be one" yet
what is the benefit of force they as one API beside "it sounds correct"?
as i mention before, i can not think of any usage of history server for
streaming application
only "The API should be one" drive it to implement just for consistency
its not necessary if you agree they are not the same
and actually
"/api/v1/application/:id/:attempt/streaming" doesn't looks logical to me
any more
in the structure speaking
streaming "use" core to process the batch.
in a streaming application, it is StreamingContext start first and it
create SparkContext
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
