[
https://issues.apache.org/jira/browse/GOBBLIN-1870?focusedWorklogId=875045&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-875045
]
ASF GitHub Bot logged work on GOBBLIN-1870:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Aug/23 01:19
Start Date: 08/Aug/23 01:19
Worklog Time Spent: 10m
Work Description: umustafi opened a new pull request, #3733:
URL: https://github.com/apache/gobblin/pull/3733
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
- [X] 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-1870
### Description
- [X] Here are some details about my PR, including screenshots (if
applicable):
Seeing the following issue when trying to acquire lease for a flow action:
`java.sql.SQLIntegrityConstraintViolationException: Column
'flow_execution_id' cannot be null" `
Flow action is created in orchestrate function, during refactoring missed
executing the line to add flow execution id to metadata to be extracted for
multi-active case. Adding a log line as well to check the flow action object
created and verify it has all the flow information.
### Tests
- [X] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [X] 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: 875045)
Remaining Estimate: 0h
Time Spent: 10m
> Fix missing flow execution id bug causing SQL Error
> ---------------------------------------------------
>
> Key: GOBBLIN-1870
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1870
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Urmi Mustafi
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Seeing the following issue when trying to acquire lease for a flow action:
> {{ava.sql.SQLIntegrityConstraintViolationException: Column
> 'flow_execution_id' cannot be null" }}
> Flow action is created in orchestrate function, during refactoring missed
> executing the line to add flow execution id to metadata to be extracted for
> multi-active case. Adding a log line as well to check the flow action object
> created and verify it has all the flow information.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
