You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "VISHNU S NAIR (JIRA)" <ji...@apache.org> on 2016/02/17 07:40:18 UTC

[jira] [Updated] (SQOOP-2839) Sqoop import failure due to data member conflict in ORM code for table

     [ https://issues.apache.org/jira/browse/SQOOP-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

VISHNU S NAIR updated SQOOP-2839:
---------------------------------
    Attachment: 0001-SQOOP-2839.patch

Patch For Issue SQOOP-2839

> Sqoop import failure due to data member conflict in ORM code for table
> ----------------------------------------------------------------------
>
>                 Key: SQOOP-2839
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2839
>             Project: Sqoop
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.4.6
>            Reporter: VISHNU S NAIR
>         Attachments: 0001-SQOOP-2839.patch
>
>
> While importing data with Sqoop, if any of the table contains a column named "PROTOCOL_VERSION", Sqoop will fail to import data.
> /tmp/sqoop-user/compile/fd570d817e8323d1135a7f2a6612e321/QueryResult.java:173: error: variable PROTOCOL_VERSION is already defined in class QueryResult
>   private String PROTOCOL_VERSION;
>                  ^
> /tmp/sqoop-user/compile/fd570d817e8323d1135a7f2a6612e321/QueryResult.java:175: error: incompatible types
>     return PROTOCOL_VERSION;
>            ^
>   required: String
>   found:    int



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