[PySparkling] Client Separation from Spark Driver

Description

In PySparkling, ensure external backend can run without h2o client on spark driver side.

The goal of this change is to ensure:
-> No H2O on Spark Driver
-> Don’t need extended H2O JAR in case of PySparkling on external backend
-> The conversion from DataFrame to H2OFrame and back needs to go without running H2O

→ Implement proxy to flow UI on one of the worker nodes → leader node

Assignee

Jakub Hava

Reporter

Jakub Hava

Labels

None

CustomerVisible

No

testcase 1

None

testcase 2

None

testcase 3

None

h2ostream link

None

Affected Spark version

None

AffectedContact

None

AffectedCustomers

None

AffectedPilots

None

AffectedOpenSource

None

Support Assessment

None

Customer Request Type

None

Support ticket URL

None

End date

None

Baseline start date

None

Baseline end date

None

Task progress

None

Task mode

None

ReleaseNotesHidden

None

Fix versions

Priority

Major

Epic Name

[External Backend] Client Separation
Configure