[
https://issues.apache.org/jira/browse/GOBBLIN-2089?focusedWorklogId=923943&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923943
]
ASF GitHub Bot logged work on GOBBLIN-2089:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jun/24 17:27
Start Date: 18/Jun/24 17:27
Worklog Time Spent: 10m
Work Description: abhishekmjain commented on PR #3975:
URL: https://github.com/apache/gobblin/pull/3975#issuecomment-2176616741
> I'm presuming that `curli -v` would show the request returning 404 as the
HTTP status...
>
> if so, change looks great!
Thanks for sharing this command, I wasn't aware of that.
Yes it indeed returns 404 status code as shown in below screenshot

Issue Time Tracking
-------------------
Worklog Id: (was: 923943)
Time Spent: 0.5h (was: 20m)
> Fix /flowexecutions KILL and RESUME action to return HTTP 404 when flow
> execution doesn't exist
> -----------------------------------------------------------------------------------------------
>
> Key: GOBBLIN-2089
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2089
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-restli
> Reporter: Abhishek Jain
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When resume or killed is called for a FlowExecution which doesn't exist, we
> return 200 HttpStatus code currently.
> We should return 404 in such scenarios.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)