spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Shreedharan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-3146) Improve the flexibility of Spark Streaming Kafka API to offer user the ability to process message before storing into BM
Date Fri, 19 Dec 2014 22:24:13 GMT

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

Hari Shreedharan commented on SPARK-3146:
-----------------------------------------

For now, I am ok with just adding it to individual DStreams, not necessarily evverything -
though that would be the best case. Unfortunately, that would break the current interface
(unless of course we add an implementation) - though since each event is received by individual
receivers, using this means the receiver would need to call a method like "intercept" or something.
Either way, I am also a strong +1 on getting this in soon!

> Improve the flexibility of Spark Streaming Kafka API to offer user the ability to process
message before storing into BM
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-3146
>                 URL: https://issues.apache.org/jira/browse/SPARK-3146
>             Project: Spark
>          Issue Type: Improvement
>          Components: Streaming
>    Affects Versions: 1.0.2, 1.1.0
>            Reporter: Saisai Shao
>
> Currently Spark Streaming Kafka API stores the key and value of each message into BM
for processing, potentially this may lose the flexibility for different requirements:
> 1. currently topic/partition/offset information for each message is discarded by KafkaInputDStream.
In some scenarios people may need this information to better filter the message, like SPARK-2388
described.
> 2. People may need to add timestamp for each message when feeding into Spark Streaming,
which can better measure the system latency.
> 3. Checkpointing the partition/offsets or others...
> So here we add a messageHandler in interface to give people the flexibility to preprocess
the message before storing into BM. In the meantime time this improvement keep compatible
with current API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message