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

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-13261:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: stale-P2, 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)