[
https://issues.apache.org/jira/browse/GOBBLIN-2062?focusedWorklogId=923043&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-923043
]
ASF GitHub Bot logged work on GOBBLIN-2062:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jun/24 22:04
Start Date: 11/Jun/24 22:04
Worklog Time Spent: 10m
Work Description: phet opened a new pull request, #3944:
URL: https://github.com/apache/gobblin/pull/3944
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I
have checked off all the steps below!
### JIRA
- [ ] My PR addresses the following [Gobblin
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
- https://issues.apache.org/jira/browse/GOBBLIN-2062
### Description
- [ ] Here are some details about my PR, including screenshots (if
applicable):
the Orchestrator + DagManager MUST remove adhoc flows from the FlowCatalog
that fail compilation or violate concurrent execs. otherwise gaas will continue
to return '409 Conflict' to each subsequent attempt to subsequently create an
adhoc flow with the same flowGroup+flowName. this is despite the fact that the
flow (still remaining in the FlowCatalog, when it shouldn't be) already has the
status of FAILED, which is a "final status".
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
added test cases (herein)
### Commits
- [ ] My commits all reference JIRA issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
Issue Time Tracking
-------------------
Worklog Id: (was: 923043)
Time Spent: 5h 20m (was: 5h 10m)
> adhoc flow failure due to concurrent execs must be removed from flow catalog
> ----------------------------------------------------------------------------
>
> Key: GOBBLIN-2062
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2062
> Project: Apache Gobblin
> Issue Type: New Feature
> Components: gobblin-service
> Reporter: Kip Kohn
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> the Orchestrator + DagManager MUST remove adhoc flows that violate concurrent
> execs from the flow catalog. otherwise gaas will continue to return '409
> Conflict' to each subsequent attempt to create an adhoc flow with the same
> flowGroup+flowName. this is despite the fact that the flow (which still
> remains in the FlowCatalog, when it shouldn't be) already has the status
> FAILED, which is a "final status".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
