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

    https://github.com/apache/spark/pull/2940#discussion_r19498298
  
    --- Diff: 
streaming/src/main/scala/org/apache/spark/streaming/receiver/ReceivedBlockHandler.scala
 ---
    @@ -0,0 +1,144 @@
    +package org.apache.spark.streaming.receiver
    +
    +import java.nio.ByteBuffer
    +
    +import scala.collection.mutable.ArrayBuffer
    +import scala.concurrent.{Await, ExecutionContext, Future}
    +import scala.concurrent.duration._
    +import scala.language.{existentials, postfixOps}
    +
    +import WriteAheadLogBasedBlockHandler._
    +import org.apache.hadoop.conf.Configuration
    +import org.apache.hadoop.fs.Path
    +import org.apache.spark.{SparkException, Logging, SparkConf}
    +import org.apache.spark.storage.{BlockManager, StorageLevel, StreamBlockId}
    +import org.apache.spark.streaming.util.{Clock, SystemClock, 
WriteAheadLogManager}
    +import org.apache.spark.util.Utils
    +
    +private[streaming] sealed trait ReceivedBlock
    +private[streaming] case class ArrayBufferBlock(arrayBuffer: 
ArrayBuffer[_]) extends ReceivedBlock
    +private[streaming] case class IteratorBlock(iterator: Iterator[_]) extends 
ReceivedBlock
    +private[streaming] case class ByteBufferBlock(byteBuffer: ByteBuffer) 
extends ReceivedBlock
    +
    +
    +/** Trait that represents a class that handles the storage of blocks 
received by receiver */
    +private[streaming] trait ReceivedBlockHandler {
    +
    +  /** Store a received block with the given block id */
    +  def storeBlock(blockId: StreamBlockId, receivedBlock: ReceivedBlock): 
Option[AnyRef]
    --- End diff --
    
    Is there value to having a shared trait here if you just return 
`Option[AnyRef]`? Why not just have two types of `ReceivedBlockHandler` that 
don't share a parent class. The caller cannot interact with them in an 
interchangeable way anyways, it needs to check the return type.
    
    Also, could you specify the failure handling semantics for these storeBlock 
methods? Are they supposed to throw an exception on failure?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

Reply via email to