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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/13 23:29:00 UTC

[jira] [Commented] (BEAM-13261) JDBC IO: expose max pool connections as a setting

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

Kenneth Knowles commented on BEAM-13261:
----------------------------------------

This seems useful and might be straightforward. Would you be interested in joining the community with a fix? :-)

> JDBC IO: expose max pool connections as a setting
> -------------------------------------------------
>
>                 Key: BEAM-13261
>                 URL: https://issues.apache.org/jira/browse/BEAM-13261
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-jdbc
>    Affects Versions: 2.33.0
>         Environment: Dataflow
>            Reporter: Kyrylo Panarin
>            Priority: P2
>              Labels: starter
>
> This is related to [BEAM-9629](https://issues.apache.org/jira/browse/BEAM-9629) and [this]([https://github.com/spotify/scio/issues/4047).] In some cases users need to have an option to bump number of max connections in the pool, but as of today the process of overriding the number isn't user friendly. Would be helpful to have this as a separate first class JDBC setting a user can configure.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)