Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 938801763F for ; Tue, 21 Oct 2014 13:40:34 +0000 (UTC) Received: (qmail 75713 invoked by uid 500); 21 Oct 2014 13:40:34 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 75675 invoked by uid 500); 21 Oct 2014 13:40:34 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 75662 invoked by uid 99); 21 Oct 2014 13:40:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 13:40:34 +0000 Date: Tue, 21 Oct 2014 13:40:34 +0000 (UTC) From: "Jarek Jarcec Cecho (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (SQOOP-1551) Repository Upgrader api - Extensibility MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SQOOP-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho resolved SQOOP-1551. --------------------------------------- Resolution: Fixed Fix Version/s: 1.99.4 Thank you for your contribution [~vybs]! > Repository Upgrader api - Extensibility > --------------------------------------- > > Key: SQOOP-1551 > URL: https://issues.apache.org/jira/browse/SQOOP-1551 > Project: Sqoop > Issue Type: Sub-task > Affects Versions: 1.99.4 > Reporter: Veena Basavaraj > Assignee: Veena Basavaraj > Fix For: 1.99.4 > > Attachments: SQOOP-1551.patch, SQOOP-1551.patch, SQOOP-1551.patch, SQOOP-1551.patch, SQOOP-1551.patch, 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)