Brandon Freeman
09/06/2023, 12:47 PM404
when hitting the localhost:8006/v1/jobs/{job_id}
endpoint for valid `job_id`s in my v0.50.14
OSS implementation.
Seems that others are experiencing the same with v0.50.24
.
Hitting /v1/jobs?status=running
I'll get the expected output:
{'data': [
{
'connectionId': 'aaeb5f07-76dc-4b0a-9498-40f26c4cdfe4',
'duration': 'PT0S',
'jobId': 4442,
'jobType': 'sync',
'startTime': '2023-09-05T22:15:43Z',
'status': 'running'
},
{
'connectionId': '52342a79-b9f7-4258-ad53-d067d0340c6e',
'duration': 'PT0S',
'jobId': 4439,
'jobType': 'sync',
'startTime': '2023-09-05T16:08:52Z',
'status': 'running'
}
]}
Yet when I make the call to /v1/jobs/4442
or /v1/jobs/4439
I simply get a 404 - Not Found
response.Jonathan Neo
09/06/2023, 2:13 PMJonathan Neo
09/06/2023, 2:14 PM<http://localhost:8006/v1/jobs/{jobId}>
https://reference.airbyte.com/reference/getjobJonathan Neo
09/06/2023, 2:15 PMBrandon Freeman
09/06/2023, 2:17 PM<http://localhost:8006>
was impliedJonathan Neo
09/06/2023, 2:17 PMjobs
and not job
Jonathan Neo
09/06/2023, 2:17 PMjob_id = 38
url = "<http://localhost:8000/api/v1/jobs/get>"
data = {
"id": job_id
}
job_response = <http://requests.post|requests.post>(url=url, json=data, headers=headers)
Brandon Freeman
09/06/2023, 2:18 PMJonathan Neo
09/06/2023, 2:18 PM