You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Stephen Sisk (JIRA)" <ji...@apache.org> on 2017/06/12 16:56:00 UTC

[jira] [Commented] (BEAM-1323) Add parallelism/splitting in JdbcIO

    [ https://issues.apache.org/jira/browse/BEAM-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046775#comment-16046775 ] 

Stephen Sisk commented on BEAM-1323:
------------------------------------

+1 to eugene's comment. I don't believe we can reliably do this in jdbc IO in a way that works across  databases - thus, any implementation of this proposal would likely result in bad experiences for many users.

Unless you have a concrete proposal that we can prove works across many databases, I think we should close this issue.

> Add parallelism/splitting in JdbcIO
> -----------------------------------
>
>                 Key: BEAM-1323
>                 URL: https://issues.apache.org/jira/browse/BEAM-1323
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-extensions
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Now, the JDBC IO is basically a {{DoFn}} executed with a {{ParDo}}. So, it means that parallelism is "limited" and executed on one executor.
> We can imagine to create several JDBC {{BoundedSource}}s splitting the SQL query in  subset (for instance using row id paging or any "splitting/limit" we can figure based on the original SQL query) (something similar to what Sqoop is doing).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)