[jira] [Work logged] (GOBBLIN-2036) Fix bug where concurrent flow config key is parsed as boolean instead of fetched as string

[ASF GitHub Bot (Jira)]

     [ 
https://issues.apache.org/jira/browse/GOBBLIN-2036?focusedWorklogId=913051&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-913051
 ]

ASF GitHub Bot logged work on GOBBLIN-2036:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Apr/24 16:21
            Start Date: 04/Apr/24 16:21
    Worklog Time Spent: 10m 
      Work Description: umustafi commented on PR #3915:
URL: https://github.com/apache/gobblin/pull/3915#issuecomment-2037654305

   This worked before because we had the value as a string? I don't recall us 
changing the configurations, but regardless of how 
`flow.allowConcurrentExecution` is set in the configs this always interprets it 
as a string then takes the boolean value of it correct?




Issue Time Tracking
-------------------

    Worklog Id:     (was: 913051)
    Time Spent: 0.5h  (was: 20m)

> Fix bug where concurrent flow config key is parsed as boolean instead of 
> fetched as string
> ------------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-2036
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2036
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: William Lo
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The old value of 
> {code:java}
> flow.allowConcurrentExecution{code}
> is set as a string value in the flow configuration jsons, but in the code we 
> parse it as boolean. Instead we want to parse as string then convert to 
> boolean to make this backwards compatible with existing flow configs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)