[
https://issues.apache.org/jira/browse/SQOOP-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149183#comment-15149183
]
Jarek Jarcec Cecho commented on SQOOP-2839:
-------------------------------------------
Hi [~vishnusn],
we're really not accepting a pull requests right now, would you mind uploading
a patch to the JIRA itself?
I'm also wondering, rather then changing the variable name and thus just
delaying the problem, wound't it make more sense to add that name to our
[protected
list|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/orm/ClassWriter.java#L60]?
> 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
>
> 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)
