You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Tak Lon (Stephen) Wu (JIRA)" <ji...@apache.org> on 2019/03/27 16:10:00 UTC

[jira] [Created] (SQOOP-3435) SqoopOptions missed a null checking

Tak Lon (Stephen) Wu created SQOOP-3435:
-------------------------------------------

             Summary: SqoopOptions missed a null checking
                 Key: SQOOP-3435
                 URL: https://issues.apache.org/jira/browse/SQOOP-3435
             Project: Sqoop
          Issue Type: Bug
    Affects Versions: 1.4.7, 1.5.0
            Reporter: Tak Lon (Stephen) Wu


in [SqoopOptions.java#L785|https://github.com/apache/sqoop/blob/branch-1.4.7/src/java/org/apache/sqoop/SqoopOptions.java#L785] {{SqoopJsonUtil.getJsonStringforMap((Map) f.get(this)));}} should check null pointer like [SqoopOptions.java#L778|https://github.com/apache/sqoop/blob/branch-1.4.7/src/java/org/apache/sqoop/SqoopOptions.java#L778] {{f.get(this) == null ? "null" : f.get(this).toString()}} 

Please see the stacktrace here

{code}
19/02/02 01:09:21 ERROR sqoop.Sqoop: Got exception running Sqoop: java.lang.NullPointerException
java.lang.NullPointerException
at org.json.JSONObject.<init>(JSONObject.java:144)
at org.apache.sqoop.util.SqoopJsonUtil.getJsonStringforMap(SqoopJsonUtil.java:43)
at org.apache.sqoop.SqoopOptions.writeProperties(SqoopOptions.java:785)
at org.apache.sqoop.metastore.hsqldb.HsqldbJobStorage.createInternal(HsqldbJobStorage.java:399)
at org.apache.sqoop.metastore.hsqldb.HsqldbJobStorage.create(HsqldbJobStorage.java:379)
at org.apache.sqoop.tool.JobTool.createJob(JobTool.java:181)
at org.apache.sqoop.tool.JobTool.run(JobTool.java:294)
at org.apache.sqoop.Sqoop.run(Sqoop.java:147)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:183)
at org.apache.sqoop.Sqoop.runTool(Sqoop.java:234)
at org.apache.sqoop.Sqoop.runTool(Sqoop.java:243)
at org.apache.sqoop.Sqoop.main(Sqoop.java:252)

{code}

Reporting this bug and the right behavior need to be decided by the assignee.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)