[
https://issues.apache.org/jira/browse/SQOOP-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162938#comment-14162938
]
Veena Basavaraj commented on SQOOP-1551:
----------------------------------------
#1 - + 1 from the team, we shall call it ConfigurableUpgrader
#2 - + 1 from the team as well, if we can come up with a upgrade api to
support different types. Alternative have a upgrader api per Configurable.
{code}
ConnectorConfigUpgrader ( as a base class) with upgradeLink, upgradeFrom,
upgradeTo
{code}
{code}
DriverConfigUpgrader ( as a a base class )with upgradeJobConfig and later on
add things if we have more config types
{code}
#3. + 1 from the team
#4, we all agree that connector config/ driver config should be run from the
Sqoop during startup/ or some other time but still controlled by Sqoop
#5 +1 from the team
> Repository Upgrader api - Extensibility
> ---------------------------------------
>
> Key: SQOOP-1551
> URL: https://issues.apache.org/jira/browse/SQOOP-1551
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: SQOOP-1551.patch
>
>
> I am not sure if the current api is extensible enough. It only supports
> upgrading the config info. Which actually can be now done via the rest api as
> well. So do we really need this config upgrade api was my first thought?
> I am also not sure how this code supports upgrades across different versions,
> since there seems to be no code in any of these that has knowledge of the
> repository version and what type of repository it really belongs to
> Split the api into
> ConnectorConfigUpgrader
> upgradeLinkConfig
> upgradeFromJobConfig
> upgradeToJobConfig
> DriverConfig Upgrader
> upgradeDriverConfig
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
