You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/04/18 13:00:43 UTC
[jira] [Assigned] (BEAM-1995) JdbcIO.Write randomly fails
PreparedStatements due to missing variables
[ https://issues.apache.org/jira/browse/BEAM-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned BEAM-1995:
------------------------------------------
Assignee: Jean-Baptiste Onofré (was: Davor Bonaci)
> JdbcIO.Write randomly fails PreparedStatements due to missing variables
> -----------------------------------------------------------------------
>
> Key: BEAM-1995
> URL: https://issues.apache.org/jira/browse/BEAM-1995
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-extensions
> Reporter: Rik Nauta
> Assignee: Jean-Baptiste Onofré
>
> I'm still investigating but it seems that the JdbcIO.Write fails randomly when submitting batches of mutations with the following types of error messages ```No value specified for parameter 1```.
> The strange thing is that it works perfectly with the DirectExecution pipeline, only when it's submitted to DataFlow does it fail. Also, if I modify the code to not batch requests but immediately commit them (manually, autocommit is still off) then it completes without errors.
> I've checked the input data which is correct so it's either an issue with the JDBC driver or I suspect that there might be some kind of concurrency issue that only shows when the pipeline is executed parallel? Maybe the PreparedStatement should be transient or something like in other PTransforms?
> As I said, I'm still investigating but would love some assistance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)