You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/11/14 18:40:34 UTC
[jira] [Commented] (SQOOP-1728) Sqoop2: Force HDFS connector as a
configurable fixes
[ https://issues.apache.org/jira/browse/SQOOP-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212523#comment-14212523 ]
Veena Basavaraj commented on SQOOP-1728:
----------------------------------------
Still needs a sqoop 2 fix.
> Sqoop2: Force HDFS connector as a configurable fixes
> ----------------------------------------------------
>
> Key: SQOOP-1728
> URL: https://issues.apache.org/jira/browse/SQOOP-1728
> Project: Sqoop
> Issue Type: Bug
> Components: docs
> Affects Versions: 1.99.4
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.4
>
> Attachments: SQOOP-1728-1.99.4.patch, SQOOP-1728-1.99.4.patch
>
>
> THe HDFS connector is a first class citizen as a connector( configurable) in 1.99.4. Its is converted to a first class citizen as part of the repository manager upgrade.
> The repository manager is upgrading the schema first and then force creating a new connector called HDFS in it.
> This code needs to match the code names used for configs and its inputs, if not the validation will fail during upgrade.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)