[jira] [Commented] (SPARK-34596) NewInstance.doGenCode should not throw malformed class name error

["Apache Spark (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-34596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293632#comment-17293632 ] 

Apache Spark commented on SPARK-34596:
--------------------------------------

User 'rednaxelafx' has created a pull request for this issue:
https://github.com/apache/spark/pull/31709

> NewInstance.doGenCode should not throw malformed class name error
> -----------------------------------------------------------------
>
>                 Key: SPARK-34596
>                 URL: https://issues.apache.org/jira/browse/SPARK-34596
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.7, 3.0.2, 3.1.0
>            Reporter: Kris Mok
>            Priority: Major
>
> Similar to SPARK-32238 and SPARK-32999, the use of {{java.lang.Class.getSimpleName}} in {{NewInstance.doGenCode}} 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 (fixed in the JDK by https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8057919), 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