[jira] [Updated] (SPARK-23453) ToolBox compiled Spark UDAF causes java.lang.InternalError: Malformed class name

2018-02-16 Thread Eric Lo (JIRA)

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

Eric Lo updated SPARK-23453:

Description: 
Here is a weird problem I just ran into... My scenario is that I need to 
compile UDAF dynamically at runtime but it never worked.

I am using Scala 2.11.11 and Spark 2.2.1, please refer to my [StackOverflow 
post|https://stackoverflow.com/questions/48820212/toolbox-compiled-spark-udaf-causes-java-lang-internalerror-malformed-class-name]
 for detailed information and minimal examples. The problem itself is very 
similar to other Malformed class name tickets (for example  
-[https://github.com/apache/spark/pull/9568])-  which were caused by calling 
getSimpleName of nested class/object but actually it is different in this case 
and the problem is still there. The getSimpleName issue has been fixed in Java 
9 which Spark doesn't support it yet...so...any solution/workaround is 
appreciated.

  was:
Here is a weird problem I just ran into... My scenario is that I need to 
compile UDAF dynamically at runtime but it never worked.

I am using Scala 2.11.11 and Spark 2.2.1, please refer to my [StackOverflow 
post|https://stackoverflow.com/questions/48820212/toolbox-compiled-spark-udaf-causes-java-lang-internalerror-malformed-class-name]
 for detailed information. The problem itself is very similar to other 
Malformed class name tickets (for example - 
[https://github.com/apache/spark/pull/9568]) - which were caused by calling 
getSimpleName of nested class/object but actually it is different in this case 
and the problem is still there. The getSimpleName issue has been fixed in Java 
9 which Spark doesn't support it yet...so...any solution/workaround is 
appreciated.


> ToolBox compiled Spark UDAF causes java.lang.InternalError: Malformed class 
> name
> 
>
> Key: SPARK-23453
> URL: https://issues.apache.org/jira/browse/SPARK-23453
> Project: Spark
>  Issue Type: Bug
>  Components: Spark Core
>Affects Versions: 2.2.1
> Environment: Spark 2.2.1
> Scala 2.11.11
> JDK 1.8
>Reporter: Eric Lo
>Priority: Major
>
> Here is a weird problem I just ran into... My scenario is that I need to 
> compile UDAF dynamically at runtime but it never worked.
> I am using Scala 2.11.11 and Spark 2.2.1, please refer to my [StackOverflow 
> post|https://stackoverflow.com/questions/48820212/toolbox-compiled-spark-udaf-causes-java-lang-internalerror-malformed-class-name]
>  for detailed information and minimal examples. The problem itself is very 
> similar to other Malformed class name tickets (for example  
> -[https://github.com/apache/spark/pull/9568])-  which were caused by calling 
> getSimpleName of nested class/object but actually it is different in this 
> case and the problem is still there. The getSimpleName issue has been fixed 
> in Java 9 which Spark doesn't support it yet...so...any solution/workaround 
> is appreciated.



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

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



[jira] [Created] (SPARK-23453) ToolBox compiled Spark UDAF causes java.lang.InternalError: Malformed class name

2018-02-16 Thread Eric Lo (JIRA)
Eric Lo created SPARK-23453:
---

 Summary: ToolBox compiled Spark UDAF causes 
java.lang.InternalError: Malformed class name
 Key: SPARK-23453
 URL: https://issues.apache.org/jira/browse/SPARK-23453
 Project: Spark
  Issue Type: Bug
  Components: Spark Core
Affects Versions: 2.2.1
 Environment: Spark 2.2.1
Scala 2.11.11
JDK 1.8
Reporter: Eric Lo


Here is a weird problem I just ran into... My scenario is that I need to 
compile UDAF dynamically at runtime but it never worked.

I am using Scala 2.11.11 and Spark 2.2.1, please refer to my [StackOverflow 
post|https://stackoverflow.com/questions/48820212/toolbox-compiled-spark-udaf-causes-java-lang-internalerror-malformed-class-name]
 for detailed information. The problem itself is very similar to other 
Malformed class name tickets (for example - 
[https://github.com/apache/spark/pull/9568]) - which were caused by calling 
getSimpleName of nested class/object but actually it is different in this case 
and the problem is still there. The getSimpleName issue has been fixed in Java 
9 which Spark doesn't support it yet...so...any solution/workaround is 
appreciated.



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

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