[
https://issues.apache.org/jira/browse/SQOOP-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1554:
-----------------------------------
Description: (was: The name is misleading again, it is doing the config
data upgrade.
Repository upgrade might mean that the schema for the repository is changing
and it is not the intention here. This api supports upgrading the connector and
driver configs per type. Right now we have 2 types. I wonder if this api can be
more generic
{code}
public abstract class RepositoryUpgrader {
/**
* Upgrade the original link config and fill into the upgradeTarget. Note
* that any data already in {@code upgradeTarget} maybe overwritten.
* @param original - original link config as in the repository
* @param upgradeTarget - the instance that will be filled in with the
* upgraded link config.
*/
public abstract void upgrade(MLinkConfig original, MLinkConfig upgradeTarget);
/**
* Upgrade the original job config and fill into the upgradeTarget. Note
* that any config data already in {@code upgradeTarget} maybe overwritten.
* This method must be called only after the link config has
* already been upgraded.
* @param original - original job config as in the repository
* @param upgradeTarget - the instance that will be filled in with the
* upgraded job config.
* NOTE(VB): This api will be revisited to accomodate from and to job config
update
*/
public abstract void upgrade(MConfigList original, MConfigList upgradeTarget);
}
{code} )
> Cleanup Repository api to retrofit with the config renames and from/to job
> configs
> ----------------------------------------------------------------------------------
>
> Key: SQOOP-1554
> URL: https://issues.apache.org/jira/browse/SQOOP-1554
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
