Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
ok,thanks.
---
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,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17841
Unless somebody says this isn't a private API, let's close this PR
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17841
Nobody is suggesting it doesn't work. It is at least only known to work to
support internal callers. It is subject to changes in the API. A public API in
contrast needs to retain compatibility over
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
Where is the risk? High concurrency? Transaction processing? This is where
I am puzzled.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17841
I think @srowen already clarified it very clearly, you can use it at your
own risk, but to make it public and add to the doc should be well considered.
---
If your project is set up for it, you
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
@jerryshao
I said that the use of the scene is real, do you agree?
---
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
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
In fact, the three api is three servlets, submitRequestServlet,
killRequestServlet, statusRequestServlet. Theoretically should be open to
enhance the function of spark.
As for why not
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17841
It is not documented because it is not something you should call. You do so
at your own risk. Documentation is appropriate for supported APIs only.
---
If your project is set up for it, you can
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
@srowen
I'm sorry, I did not understand what you meant. Can you give me a detailed
analysis? Thank you.
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17841
He is saying you are not intended to call this API.
---
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
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17841
@jerryshao
Yes, we now have the need to use REST APIs to submit SPARK jobs.
We submit the task of submitting a application to a WEB system, which is
designed to manage the
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17841
I remember these REST APIs are not public APIs, it is only used for
SparkSubmit internally. shall we add the docs about them?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17841
Can one of the admins verify this patch?
---
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
13 matches
Mail list logo
