[
https://issues.apache.org/jira/browse/SQOOP-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790736#comment-14790736
]
Hudson commented on SQOOP-2464:
-------------------------------
SUCCESS: Integrated in Sqoop2 #897 (See
[https://builds.apache.org/job/Sqoop2/897/])
SQOOP-2464: Initializer object is not reused when calling getSchema (jarcec:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=f241f82c3824dc6e0ef23968712569f81c1d10ee)
* core/src/main/java/org/apache/sqoop/driver/JobManager.java
*
connector/connector-sdk/src/main/java/org/apache/sqoop/job/etl/Initializer.java
* docs/src/site/sphinx/ConnectorDevelopment.rst
> Initializer object is not reused when calling getSchema
> -------------------------------------------------------
>
> Key: SQOOP-2464
> URL: https://issues.apache.org/jira/browse/SQOOP-2464
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: David Robson
> Assignee: Abraham Fine
> Fix For: 1.99.7
>
> Attachments: SQOOP-2464.patch
>
>
> In JobManager there is two methods which are called one after the other -
> "initializeConnector" and "getSchemaForConnector". Both these methods do the
> same thing as the first step - create a new instance of the initializer class.
> If the same instance of the initializer was shared it means the class could
> keep resources open (such as a connection to the database) and not have to
> re-establish the connection. This might mean a close method needs to be added
> to the initializers as otherwise the getSchema would need to close any
> resources opened in the initialize call - which might seem a bit confusing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
