[ 
https://issues.apache.org/jira/browse/SQOOP-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218118#comment-14218118
 ] 

ASF subversion and git services commented on SQOOP-1728:
--------------------------------------------------------

Commit dfd1fd34815f339087364d73de61a30fb941e093 in sqoop's branch 
refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=dfd1fd3 ]

SQOOP-1733: Port SQOOP-1728 to sqoop2 branch

(Abraham Elmahrek via Jarek Jarcec Cecho)


> 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-v2.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)

Reply via email to