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

Berwanman Wendhy commented on SQOOP-368:
----------------------------------------

Hi...I got same issue like this, and I want to apply this patch in my 
environment. Sqoop version that I'm using is 1.4.6, can I know which file that 
I need to patch ?

Thanks

Berwanman

> Resolve ERROR tool.ImportTool: Imported Failed: Duplicate Column identifier 
> specified: 'COLUMN-NAME'
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-368
>                 URL: https://issues.apache.org/jira/browse/SQOOP-368
>             Project: Sqoop
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 1.4.0-incubating
>         Environment: 64bit Ubuntu 10.10 Linux, Java build 1.6.0_24-b07, mysql 
> 5.1.49-1ubuntu8.1
>            Reporter: guoyun
>            Assignee: guoyun
>              Labels: alias, column, import, mysql, query, sqoop
>             Fix For: 1.4.0-incubating
>
>         Attachments: import-support-query-column-alias-v1.patch, 
> query-column.alias.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> for execute this command:
> import --connect jdbc:mysql://localhost/sqoop_datas  --username root 
> --password 123456 --query "select sqoop_source_datas.id as foo_id, sqoop_2.id 
> as bar_id from sqoop_source_datas ,sqoop_2  WHERE $CONDITIONS" --target-dir 
> /tmp/sqoop/foo -split-by foo_id   
> --hadoop-home=/home/guoyun/Downloads/hadoop-0.20.2-CDH3B4
> because table sqoop_source_datas and table sqoop_2 have the same column:id.so 
> it will report error:resolve ERROR tool.ImportTool: Imported Failed: 
> Duplicate Column identifier specified: 'ID'
> For patch:query-column.alias.patch,we must set the parameter split-by to real 
> column name.for my example,i must set split-by to sqoop_source_datas.id,not 
> foo_id



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to