[
https://issues.apache.org/jira/browse/SQOOP-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598028#comment-13598028
]
Hudson commented on SQOOP-936:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop200 #578 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/578/])
SQOOP-936: Classwriter should check if columnNames generated are null
before accessing them (Revision 1d0ebc27308609a21f3762a64019098b4ae36e6e)
Result = SUCCESS
jarcec :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=1d0ebc27308609a21f3762a64019098b4ae36e6e
Files :
* src/java/org/apache/sqoop/orm/ClassWriter.java
> Classwriter should check if columnNames generated are null before accessing
> them
> --------------------------------------------------------------------------------
>
> Key: SQOOP-936
> URL: https://issues.apache.org/jira/browse/SQOOP-936
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.2, 1.4.3
> Environment: Netezza database tests
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Minor
> Labels: trivial
> Fix For: 1.4.4
>
> Attachments: SQOOP-936.patch
>
>
> If a table does not at the time of DROP, Netezza throws an exception but also
> sets the transaction as ignored (all changes through the connection will be
> ignored until the txn is either rollback or committed. While adding more
> tests, I missed the rollback and the create table was ignored, and
> subsequently ClassWriter.cleanColNames() threw NPE. I am fixing Netezza
> tests also, but we should check for this and throw a IOException instead of
> failing with NPE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
