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

Paul Zaczkieiwcz commented on SPARK-18055:
------------------------------------------

[~marmbrus]: I ran into this issue when using a custom 
org.apache.spark.sql.expressions.Aggregator in Spark 2.0.2.

{code:java}
val aggregator:Aggregator = ....
df.groupByKey(s => CookieId(s.cookie_id)
).agg(aggregator.toColumn)
{code}

I got a very similar {{scala.ScalaReflectionException}}, which is how I found 
this ticket. Is there an easy way around this short of either converting my 
brand-new {{Aggregator}} into a {{UserDefinedAggregateFunction}} or custom 
installing a patched version of Spark onto my cluster?

> Dataset.flatMap can't work with types from customized jar
> ---------------------------------------------------------
>
>                 Key: SPARK-18055
>                 URL: https://issues.apache.org/jira/browse/SPARK-18055
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.0.1
>            Reporter: Davies Liu
>            Assignee: Michael Armbrust
>             Fix For: 2.0.3, 2.1.1, 2.2.0
>
>         Attachments: test-jar_2.11-1.0.jar
>
>
> Try to apply flatMap() on Dataset column which of of type
> com.A.B
> Here's a schema of a dataset:
> {code}
> root
>  |-- id: string (nullable = true)
>  |-- outputs: array (nullable = true)
>  |    |-- element: string
> {code}
> flatMap works on RDD
> {code}
>  ds.rdd.flatMap(_.outputs)
> {code}
> flatMap doesnt work on dataset and gives the following error
> {code}
> ds.flatMap(_.outputs)
> {code}
> The exception:
> {code}
> scala.ScalaReflectionException: class com.A.B in JavaMirror … not found
>     at scala.reflect.internal.Mirrors$RootsBase.staticClass(Mirrors.scala:123)
>     at scala.reflect.internal.Mirrors$RootsBase.staticClass(Mirrors.scala:22)
>     at 
> line189424fbb8cd47b3b62dc41e417841c159.$read$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$iw$$typecreator3$1.apply(<console>:51)
>     at 
> scala.reflect.api.TypeTags$WeakTypeTagImpl.tpe$lzycompute(TypeTags.scala:232)
>     at scala.reflect.api.TypeTags$WeakTypeTagImpl.tpe(TypeTags.scala:232)
>     at 
> org.apache.spark.sql.SQLImplicits$$typecreator9$1.apply(SQLImplicits.scala:125)
>     at 
> scala.reflect.api.TypeTags$WeakTypeTagImpl.tpe$lzycompute(TypeTags.scala:232)
>     at scala.reflect.api.TypeTags$WeakTypeTagImpl.tpe(TypeTags.scala:232)
>     at 
> org.apache.spark.sql.catalyst.encoders.ExpressionEncoder$.apply(ExpressionEncoder.scala:49)
>     at 
> org.apache.spark.sql.SQLImplicits.newProductSeqEncoder(SQLImplicits.scala:125)
> {code}
> Spoke to Michael Armbrust and he confirmed it as a Dataset bug.
> There is a workaround using explode()
> {code}
> ds.select(explode(col("outputs")))
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to