Github user CodingCat commented on a diff in the pull request:

    https://github.com/apache/spark/pull/214#discussion_r11102892
  
    --- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
    @@ -149,6 +151,21 @@ private[spark] object Utils extends Logging {
         buf
       }
     
    +  def serializeTask(taskNoSer: TaskDescWithoutSerializedTask, sc: 
SparkContext,
    +                    serializer: SerializerInstance) : TaskDescription = {
    +    val startTime = System.currentTimeMillis()
    +    // We rely on the DAGScheduler to catch non-serializable closures and 
RDDs, so in here
    --- End diff --
    
    I checked the DAGScheduler code, L793, I think it's pretty straightforward 
to move that functionality to here, as you will have an unified implementation 
of SerializerAndRunner for all scheduler 
backend....https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala#L770,
 that line is actually just for checking if the task is serializable......


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to