[
https://issues.apache.org/jira/browse/BEAM-14405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niel Markwick updated BEAM-14405:
---------------------------------
Description:
BEAM-13665 fixed the issue of NPE's when ProjectIDs were not specified in
command line executions by checking for a null ValueProvider, but in _template_
executions, the ValueProvider is non-null but has a null {_}value{_}.
PR #17094 from BEAM-14116 added nullness checks for keys in
MonitoringInfoMetricName, which then triggered the NPE in 2.38.0 when a
template was executed with an unspecified ProjectID.
was:BEAM-13665 fixed the issue of NPE's when ProjectIDs were not specified in
command line executions by checking for a null ValueProvider, but in _template_
executions, the ValueProvider is non-null but has a null {_}value{_}.
> Java Spanner IO NPE when ProjectID not specified in template executions
> -----------------------------------------------------------------------
>
> Key: BEAM-14405
> URL: https://issues.apache.org/jira/browse/BEAM-14405
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: Niel Markwick
> Assignee: Niel Markwick
> Priority: P1
> Fix For: 2.36.0
>
>
> BEAM-13665 fixed the issue of NPE's when ProjectIDs were not specified in
> command line executions by checking for a null ValueProvider, but in
> _template_ executions, the ValueProvider is non-null but has a null
> {_}value{_}.
> PR #17094 from BEAM-14116 added nullness checks for keys in
> MonitoringInfoMetricName, which then triggered the NPE in 2.38.0 when a
> template was executed with an unspecified ProjectID.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
