相关文章推荐
没有腹肌的开水瓶  ·  Exception in thread ...·  2 月前    · 
千年单身的蚂蚁  ·  Exception in thread ...·  2 月前    · 
谦虚好学的火柴  ·  Spark ...·  2 月前    · 
要出家的米饭  ·  在 Azure Databricks ...·  2 月前    · 
精明的茶叶  ·  org.apache.ibatis.ognl ...·  1 年前    · 
茫然的显示器  ·  机器学习 ...·  1 年前    · 
奋斗的炒饭  ·  image - Django ...·  1 年前    · 
Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I am writing a spark job that the dataset is pretty flexible, it's defined as Dataset[Map[String, java.io.Serializable]] .

now the problem start to show up, spark runtime complains about No Encoder found for java.io.Serializable . I've tried kyro serde, still showing the same error message.

the reason why I have to use this weird Dataset type is because I have flexible fields per Row. and the map looks like:

"a" -> 1, "b" -> "bbb", "c" -> 0.1,

is there anyway in Spark to handle this flexible dataset type?

EDIT: here is the solid code anyone can try.

import org.apache.spark.sql.{Dataset, SparkSession}
object SerdeTest extends App {
  val sparkSession: SparkSession = SparkSession
    .builder()
    .master("local[2]")
    .getOrCreate()
  import sparkSession.implicits._
  val ret: Dataset[Record] = sparkSession.sparkContext.parallelize(0 to 10)
    .map(
      t => {
        val row = (0 to t).map(
          i => i -> i.asInstanceOf[Integer]
        ).toMap
        Record(map = row)
    ).toDS()
  val repartitioned = ret.repartition(10)
  repartitioned.collect.foreach(println)
case class Record (
                  map: Map[Int, java.io.Serializable]

the above code will give you error Encoder not found:

Exception in thread "main" java.lang.UnsupportedOperationException: No Encoder found for java.io.Serializable
- map value class: "java.io.Serializable"
- field (class: "scala.collection.immutable.Map", name: "map")

found the answer, one way to solve this is to use Kyro serde framework, code change is very minimum, just need to make an implicit Encoder using Kyro and bring that into the context whenever serialization is needed.

here is the code example I got working(can directly run in IntelliJ or equivalent IDE):

import org.apache.spark.sql._
object SerdeTest extends App {
  val sparkSession: SparkSession = SparkSession
    .builder()
    .master("local[2]")
    .getOrCreate()
  import sparkSession.implicits._
  // here is the place you define your Encoder for your custom object type, like in this case Map[Int, java.io.Serializable]
  implicit val myObjEncoder: Encoder[Record] = org.apache.spark.sql.Encoders.kryo[Record]
  val ret: Dataset[Record] = sparkSession.sparkContext.parallelize(0 to 10)
    .map(
      t => {
        val row = (0 to t).map(
          i => i -> i.asInstanceOf[Integer]
        ).toMap
        Record(map = row)
    ).toDS()
  val repartitioned = ret.repartition(10)
  repartitioned.collect.foreach(
    row => println(row.map)
case class Record (
                  map: Map[Int, java.io.Serializable]

this code will produce the expected results:

Map(0 -> 0, 5 -> 5, 1 -> 1, 2 -> 2, 3 -> 3, 4 -> 4)
Map(0 -> 0, 1 -> 1, 2 -> 2)
Map(0 -> 0, 5 -> 5, 1 -> 1, 6 -> 6, 2 -> 2, 7 -> 7, 3 -> 3, 4 -> 4)
Map(0 -> 0, 1 -> 1)
Map(0 -> 0, 1 -> 1, 2 -> 2, 3 -> 3, 4 -> 4)
Map(0 -> 0, 1 -> 1, 2 -> 2, 3 -> 3)
Map(0 -> 0)
Map(0 -> 0, 5 -> 5, 1 -> 1, 6 -> 6, 2 -> 2, 3 -> 3, 4 -> 4)
Map(0 -> 0, 5 -> 5, 10 -> 10, 1 -> 1, 6 -> 6, 9 -> 9, 2 -> 2, 7 -> 7, 3 -> 3, 8 -> 8, 4 -> 4)
Map(0 -> 0, 5 -> 5, 1 -> 1, 6 -> 6, 9 -> 9, 2 -> 2, 7 -> 7, 3 -> 3, 8 -> 8, 4 -> 4)
Map(0 -> 0, 5 -> 5, 1 -> 1, 6 -> 6, 2 -> 2, 7 -> 7, 3 -> 3, 8 -> 8, 4 -> 4)
        

Thanks for contributing an answer to Stack Overflow!

  • Please be sure to answer the question. Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.