You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/09/26 23:12:00 UTC

[jira] [Resolved] (SPARK-32999) TreeNode.nodeName should not throw malformed class name error

     [ https://issues.apache.org/jira/browse/SPARK-32999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun resolved SPARK-32999.
-----------------------------------
    Fix Version/s: 3.1.0
                   3.0.2
         Assignee: Kris Mok
       Resolution: Fixed

> TreeNode.nodeName should not throw malformed class name error
> -------------------------------------------------------------
>
>                 Key: SPARK-32999
>                 URL: https://issues.apache.org/jira/browse/SPARK-32999
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.0, 3.0.0, 3.1.0
>            Reporter: Kris Mok
>            Assignee: Kris Mok
>            Priority: Major
>             Fix For: 3.0.2, 3.1.0
>
>
> Similar to SPARK-32238, the use of {{java.lang.Class.getSimpleName}} in {{TreeNode.nodeName}} is problematic because Scala classes may trigger {{java.lang.InternalError: Malformed class name}}.
> This happens more often when using nested classes in Scala (or declaring classes in Scala REPL which implies class nesting).
> Note that on newer versions of JDK the underlying malformed class name no longer reproduces, so it's less of an issue there. But on JDK8u this problem still exists so we still have to fix it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org