GitHub user vishnusn opened a pull request:
https://github.com/apache/sqoop/pull/14
[SQOOP-2839]
On our investigation we found out this is related to Sqoopâs internal
implementation. Sqoop internally creates a Java class corresponding to the
table to be imported, which contains all the column names as data members. It
also includes a constant named "PROTOCOL_VERSION" and this leads to conflict
between data members, if one of the column is named âPROTOCOL_VERSIONâ.
So in order to solve this issue , adding PROTOCOL_VERSION in reserved words
list
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vishnusn/sqoop patch-3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sqoop/pull/14.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #14
----
commit e8887a418ee916546a2fb62475546e294a9a552e
Author: vishnusn <[email protected]>
Date: 2016-02-17T06:16:01Z
[SQOOP-2839]
On our investigation we found out this is related to Sqoopâs internal
implementation. Sqoop internally creates a Java class corresponding to the
table to be imported, which contains all the column names as data members. It
also includes a constant named "PROTOCOL_VERSION" and this leads to conflict
between data members, if one of the column is named âPROTOCOL_VERSIONâ.
So in order to solve this issue , adding PROTOCOL_VERSION in reserved words
list
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
