[
https://issues.apache.org/jira/browse/BEAM-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismaël Mejía resolved BEAM-1995.
--------------------------------
Resolution: Invalid
Fix Version/s: Not applicable
This issue has not any update in the last 1.5 years, so probably is alredy ok
so I am resolving it. [~rxminus] please reopen it if still valid.
> 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: io-java-jdbc
> Reporter: Rik Nauta
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: Not applicable
>
>
> 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
(v7.6.3#76005)
