When I want to get a specific job, I can query it by jobid, however the jobid might not always be known.
My use case is the following:
- Submit job and specify a job name
- The submit call fails (because of timeout), however the job actually makes it to the slurm queue
- I want to know if my job made it to the slurm queue, hence I query
/compute/{system_name}/jobs, which gives me all the jobs, and I try to find a job with my specified name
It seems more expensive to request all jobs, when all that I am interested in is to figure out if a job with my name exists. Hence I would suggest that the jobs endpoint would accept a name=<my-name> query parameter, which can be forwarded to slurm and restrict the returned results.
When I want to get a specific job, I can query it by
jobid, however the jobid might not always be known.My use case is the following:
/compute/{system_name}/jobs, which gives me all the jobs, and I try to find a job with my specified nameIt seems more expensive to request all jobs, when all that I am interested in is to figure out if a job with my name exists. Hence I would suggest that the jobs endpoint would accept a
name=<my-name>query parameter, which can be forwarded to slurm and restrict the returned results.