From ca19078b576dc4ae7cbffc2d6806344ce5eeb8a0 Mon Sep 17 00:00:00 2001 From: Tathagata Das Date: Wed, 10 Dec 2014 16:45:21 -0800 Subject: [PATCH] Minor change --- docs/streaming-custom-receivers.md | 1 + docs/streaming-programming-guide.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/streaming-custom-receivers.md b/docs/streaming-custom-receivers.md index 912bf37c81543..0cd0a32bba8f1 100644 --- a/docs/streaming-custom-receivers.md +++ b/docs/streaming-custom-receivers.md @@ -16,6 +16,7 @@ This starts with implementing a **Receiver** ([Scala doc](api/scala/index.html#org.apache.spark.streaming.receiver.Receiver), [Java doc](api/java/org/apache/spark/streaming/receiver/Receiver.html)). A custom receiver must extend this abstract class by implementing two methods + - `onStart()`: Things to do to start receiving data. - `onStop()`: Things to do to stop receiving data. diff --git a/docs/streaming-programming-guide.md b/docs/streaming-programming-guide.md index d6332dfa944e3..ae4e079b6d30b 100644 --- a/docs/streaming-programming-guide.md +++ b/docs/streaming-programming-guide.md @@ -762,7 +762,7 @@ that no data gets lost due to any kind of failure. This leads to two kinds of re for reliable sources, one may implement an unreliable receiver that do not go into the complexity of acknowledging correctly. -The details of how to write a reliable receiver is discussed in the +The details of how to write a reliable receiver are discussed in the [Custom Receiver Guide](streaming-custom-receivers.html). ***