[
https://issues.apache.org/jira/browse/SUBMARINE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhankun Tang updated SUBMARINE-442:
-----------------------------------
Description:
Now we have the "jobs" resource in REST which can do CRUD. We also need a
"logs" API to get the job's log output. The URI could be "api/v1/logs"
It should accept parameters like "jobid". Initially, the logs could be
aggregated logs of all containers.
Streaming is preferred so that the python client can enable a fancy way for the
end-user to check logs
was:
Now we have the "jobs" resource in REST which can do CRUD. We also need a
"logs" API to get the job's log output. The URI could be "api/v1/logs"
It should accept parameters like "jobid", "jobName". Initially, the logs could
be aggregated logs of all containers.
Streaming is preferred so that the python client can enable a fancy way for the
end-user to check logs
> Support get job's log in submarine-server REST API
> --------------------------------------------------
>
> Key: SUBMARINE-442
> URL: https://issues.apache.org/jira/browse/SUBMARINE-442
> Project: Apache Submarine
> Issue Type: Sub-task
> Components: Backend Server
> Reporter: Zhankun Tang
> Priority: Major
>
> Now we have the "jobs" resource in REST which can do CRUD. We also need a
> "logs" API to get the job's log output. The URI could be "api/v1/logs"
> It should accept parameters like "jobid". Initially, the logs could be
> aggregated logs of all containers.
> Streaming is preferred so that the python client can enable a fancy way for
> the end-user to check logs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
