[
https://issues.apache.org/jira/browse/LIVY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyorgy Gal updated LIVY-347:
----------------------------
Fix Version/s: 0.10.0
(was: 0.9.0)
This issue has been moved to the 0.10.0 release as part of a bulk update. If
you feel this is moved out inappropriately, feel free to provide justification
and reset the Fix Version to 0.9.0.
> Documentation/examples on upload endpoint
> -----------------------------------------
>
> Key: LIVY-347
> URL: https://issues.apache.org/jira/browse/LIVY-347
> Project: Livy
> Issue Type: Improvement
> Components: API, Docs, Server
> Affects Versions: 0.4.0
> Reporter: Martin Durant
> Priority: Major
> Fix For: 0.10.0
>
>
> In the python livy client, there is reference to an upload command:
> https://github.com/cloudera/livy/blob/master/python-api/src/main/python/livy/client.py#L253
> This seems to point to http://server:port/sessions/<ID>/upload
> I am interested in how to upload a file not from the location of the livy
> server, but from a remote box talking to it. Furthermore, this should be an
> archive available to spark before executing workers (so that I can execute an
> environment within my upload).
> How does this end-point or client command work, what do I need to do to
> achieve the above workflow?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
