You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2016/06/30 17:01:10 UTC
[jira] [Resolved] (BEAM-142) BigQueryIO: don't unnecessarily
initialize an ExecutorService to validate parameters
[ https://issues.apache.org/jira/browse/BEAM-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik resolved BEAM-142.
----------------------------
Resolution: Fixed
Fix Version/s: 0.2.0-incubating
> BigQueryIO: don't unnecessarily initialize an ExecutorService to validate parameters
> ------------------------------------------------------------------------------------
>
> Key: BEAM-142
> URL: https://issues.apache.org/jira/browse/BEAM-142
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Reporter: Davor Bonaci
> Assignee: Lucas Amorim
> Priority: Minor
> Fix For: 0.2.0-incubating
>
>
> See http://stackoverflow.com/questions/36142464/kicking-off-dataflow-jobs-with-app-engine-errors-with-a-securityexception-on-add
> From BigQueryIO$Write$Bound.verifyTableEmpty, we call BigQueryTableInserter, which unnecessarily sets up ExecutorService for this case. As a result, the pipeline cannot be run in the App Engine environment.
> We should fix this by avoid initialization of the ExecutorService.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)