[ 
https://issues.apache.org/jira/browse/GOBBLIN-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Urmi Mustafi updated GOBBLIN-1954:
----------------------------------
    Description: When copying a flowSpec to add flowExecutionId into its 
config, all components need to be carefully duplicated to ensure compilation, 
serialization and deserialization are successful. Some pieces can easily be 
missed so instead, we add the property to the Properties object of the FlowSpec 
which is mutable. Note that we do not update the Config object to avoid large 
GC overhead from deleting and creating a new Config object. This test also 
ensures that the DagManager thread will not silently die during leadership 
changes by catching all types of Exceptions.    (was: When copying a flowSpec 
to add flowExecutionId into its config, all components need to be carefully 
duplicated to ensure compilation, serialization and deserialization are 
successful. Some pieces can easily be missed so instead, we add the property to 
the Properties object of the FlowSpec which is mutable. This test also ensures 
that the DagManager thread will not silently die during leadership changes by 
catching all types of Exceptions.  )

> Update FlowSpec Safely to Avoid Deserialization and Compilation Failure
> -----------------------------------------------------------------------
>
>                 Key: GOBBLIN-1954
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1954
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>
> When copying a flowSpec to add flowExecutionId into its config, all 
> components need to be carefully duplicated to ensure compilation, 
> serialization and deserialization are successful. Some pieces can easily be 
> missed so instead, we add the property to the Properties object of the 
> FlowSpec which is mutable. Note that we do not update the Config object to 
> avoid large GC overhead from deleting and creating a new Config object. This 
> test also ensures that the DagManager thread will not silently die during 
> leadership changes by catching all types of Exceptions.  



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

Reply via email to