ASF GitHub Bot logged work on BEAM-3500:

                Author: ASF GitHub Bot
            Created on: 11/Mar/18 17:55
            Start Date: 11/Mar/18 17:55
    Worklog Time Spent: 10m 
      Work Description: jbonofre commented on issue #4461: [BEAM-3500] "Attach" 
JDBC connection to the bundle and add DataSourceFactory allowing full control 
of the way the DataSource is created
URL: https://github.com/apache/beam/pull/4461#issuecomment-372134799
   Rebased and only expose max number of connections in the pool to end users. 
@jkff please let me know if it's OK for you ;)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 79304)
    Time Spent: 3h  (was: 2h 50m)

> JdbcIO: Improve connection management
> -------------------------------------
>                 Key: BEAM-3500
>                 URL: https://issues.apache.org/jira/browse/BEAM-3500
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-jdbc
>    Affects Versions: 2.2.0
>            Reporter: Pawel Bartoszek
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>          Time Spent: 3h
>  Remaining Estimate: 0h
> JdbcIO write DoFn acquires connection in {{@Setup}} and release it in 
> {{@Teardown}} methods, which means that connection might stay opened for days 
> in streaming job case. Keeping single connection open for so long might be 
> very risky as it's exposed to database, network etc issues.
> *Taking connection from the pool when it is actually needed*
> I suggest that connection would be taken from the connection pool in 
> {{executeBatch}} method and released when the batch is flushed. This will 
> allow the pool to take care of any returned unhealthy connections etc.
> *Make JdbcIO accept data source factory*
>  It would be nice if JdbcIO accepted DataSourceFactory rather than DataSource 
> itself. I am saying that because sink checks if DataSource implements 
> `Serializable` interface, which make it impossible to pass 
> BasicDataSource(used internally by sink) as it doesn’t implement this 
> interface. Something like:
> {code:java}
> interface DataSourceFactory extends Serializable{
>      DataSource create();
> }
> {code}

This message was sent by Atlassian JIRA

Reply via email to