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

Posted to dev@gobblin.apache.org by "Monish Vachhani (JIRA)" <ji...@apache.org> on 2018/08/01 20:15:00 UTC

[jira] [Created] (GOBBLIN-551) JdbcExtractor code in gobblin-sql module using separate connections for `extractMetadata`, `getMaxWatermark` & `getSourceCount`

Monish Vachhani created GOBBLIN-551:
---------------------------------------

             Summary: JdbcExtractor code in gobblin-sql module using separate connections for `extractMetadata`, `getMaxWatermark` & `getSourceCount`
                 Key: GOBBLIN-551
                 URL: https://issues.apache.org/jira/browse/GOBBLIN-551
             Project: Apache Gobblin
          Issue Type: Bug
            Reporter: Monish Vachhani


JdbcExtractor code in gobblin-sql module using separate connections for `extractMetadata`, `getMaxWatermark` & `getSourceCount`. All these connections don't close when jdbcSource.close method is called  for Sql Server, this causes memory leak if proxy connection is used.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)