[
https://issues.apache.org/jira/browse/SPARK-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265570#comment-14265570
]
Cody Koeninger commented on SPARK-4960:
---------------------------------------
At that point, it sounds like you're talking about an early filter rather
than an early flatmap. Should it just be T => Option[T]?
Since this ticket no longer solves the problem raised by SPARK-3146, and it
seems unlikely that patch will ever get merged, what is the concrete plan
for giving users of receiver-based kafka implementations early access to
MessageAndMetadata?
On Mon, Jan 5, 2015 at 7:48 PM, Tathagata Das (JIRA) <j...@apache.org>
> Interceptor pattern in receivers
> --------------------------------
>
> Key: SPARK-4960
> URL: https://issues.apache.org/jira/browse/SPARK-4960
> Project: Spark
> Issue Type: New Feature
> Components: Streaming
> Reporter: Tathagata Das
>
> Sometimes it is good to intercept a message received through a receiver and
> modify / do something with the message before it is stored into Spark. This
> is often referred to as the interceptor pattern. There should be general way
> to specify an interceptor function that gets applied to all receivers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
