[GitHub] sqoop pull request: [SQOOP-2839] : Sqoop import failure due to dat...

[vishnusn <gi...@git.apache.org>]

GitHub user vishnusn opened a pull request:

    https://github.com/apache/sqoop/pull/13

    [SQOOP-2839] : Sqoop import failure due to data member conflict in ORM code for table

    [SQOOP-2839] : Sqoop 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 we updated the constant name to PROTOCOL_VERSION_SQOOP_<current Version>.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vishnusn/sqoop patch-1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sqoop/pull/13.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 #13
    
----
commit 2a3d5e4027ff7118049c72190994c1c0900aa455
Author: vishnusn <vi...@gmail.com>
Date:   2016-02-15T06:58:07Z

    Update ClassWriter.java
    
    [SQOOP-2839] : Sqoop 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 we updated the constant name to PROTOCOL_VERSION_SQOOP_<current Version>.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---