[jira] [Assigned] (FLINK-9787) Change ExecutionConfig#getGlobalJobParameters to return an instance of GlobalJobParameters instead of null if no custom globalJobParameters are set yet

2019-04-08 Thread Ji Liu (JIRA)


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

Ji Liu reassigned FLINK-9787:
-

Assignee: Ji Liu

> Change ExecutionConfig#getGlobalJobParameters to return an instance of 
> GlobalJobParameters instead of null if no custom globalJobParameters are set 
> yet
> ---
>
> Key: FLINK-9787
> URL: https://issues.apache.org/jira/browse/FLINK-9787
> Project: Flink
>  Issue Type: Improvement
>  Components: API / DataStream
>Reporter: Florian Schmidt
>Assignee: Ji Liu
>Priority: Minor
> Fix For: 2.0.0
>
>
> Currently when accessing ExecutionConfig#getGlobalJobParameters this will 
> return `null` if no globalJobParameters are set. This can easily lead to 
> NullPointerExceptions when used with getGlobalJobParameters.toMap()
> An easy improvement for this would be to just return a new instance of 
> GlobalJobParameters if none is set with the empty map as the parameters
> This would be a breaking change since we expose this via 
> RuntimeContext#getExecutionConfig



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9787) Change ExecutionConfig#getGlobalJobParameters to return an instance of GlobalJobParameters instead of null if no custom globalJobParameters are set yet

2018-07-10 Thread Florian Schmidt (JIRA)


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

Florian Schmidt reassigned FLINK-9787:
--

Assignee: (was: Florian Schmidt)

> Change ExecutionConfig#getGlobalJobParameters to return an instance of 
> GlobalJobParameters instead of null if no custom globalJobParameters are set 
> yet
> ---
>
> Key: FLINK-9787
> URL: https://issues.apache.org/jira/browse/FLINK-9787
> Project: Flink
>  Issue Type: Improvement
>Reporter: Florian Schmidt
>Priority: Minor
> Fix For: 2.0.0
>
>
> Currently when accessing ExecutionConfig#getGlobalJobParameters this will 
> return `null` if no globalJobParameters are set. This can easily lead to 
> NullPointerExceptions when used with getGlobalJobParameters.toMap()
> An easy improvement for this would be to just return a new instance of 
> GlobalJobParameters if none is set with the empty map as the parameters
> This would be a breaking change since we expose this via 
> RuntimeContext#getExecutionConfig



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (FLINK-9787) Change ExecutionConfig#getGlobalJobParameters to return an instance of GlobalJobParameters instead of null if no custom globalJobParameters are set yet

2018-07-10 Thread Florian Schmidt (JIRA)


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

Florian Schmidt reassigned FLINK-9787:
--

Assignee: Florian Schmidt

> Change ExecutionConfig#getGlobalJobParameters to return an instance of 
> GlobalJobParameters instead of null if no custom globalJobParameters are set 
> yet
> ---
>
> Key: FLINK-9787
> URL: https://issues.apache.org/jira/browse/FLINK-9787
> Project: Flink
>  Issue Type: Improvement
>Reporter: Florian Schmidt
>Assignee: Florian Schmidt
>Priority: Minor
>
> Currently when accessing 
>  
> ExecutionConfig#getGlobalJobParameters this will return `null` if no 
> globalJobParameters are set. This can easily lead to NullPointerExceptions 
> when used with getGlobalJobParameters.toMap()
>  
> An easy improvement for this would be to just return a new instance of 
> GlobalJobParameters if none is set with the empty map as the parameters



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)