New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SW-2303] Create Sparkling Py4j Getaway for Steam #2173
Conversation
68c0901
to
18b0e7c
Compare
f6f70d6
to
e462b8a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks! Will try the nighly once it is out.
core/src/main/scala/ai/h2o/sparkling/backend/SparklingGateway.scala
Outdated
Show resolved
Hide resolved
core/src/main/scala/ai/h2o/sparkling/backend/SparklingGateway.scala
Outdated
Show resolved
Hide resolved
core/src/main/scala/ai/h2o/sparkling/backend/SparklingGateway.scala
Outdated
Show resolved
Hide resolved
core/src/main/scala/ai/h2o/sparkling/backend/SparklingGateway.scala
Outdated
Show resolved
Hide resolved
core/src/main/scala/ai/h2o/sparkling/backend/SparklingGateway.scala
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bilcus I have implemented the automatic port selection. Steam can then obtain the port by reading the following endpoint:
I wanted to keep it generic so the rest of our code doesn't contain references to the gateway code |
@jakubhava |
(cherry picked from commit c840139)
Steam is trying to get rid of Livy.
To achieve this, we can use the Py4j Gateway directly and allow the Spark python client to connect to remote Spark cluster without the Livy complexities.