[SPARK-28871][MINOR][DOCS] WaterMark doc fix

### What changes were proposed in this pull request?

The code style in the 'Policy for handling multiple watermarks' in structured-streaming-programming-guide.md

### Why are the changes needed?

Making it look friendly  to user.

### Does this PR introduce any user-facing change?
NO

### How was this patch tested?

    cd docs
    SKIP_API=1 jekyll build

Closes #25580 from cyq89051127/master.

Authored-by: cyq89051127 <chaiyq@asiainfo.com>
Signed-off-by: Sean Owen <sean.owen@databricks.com>
This commit is contained in:
cyq89051127 2019-08-27 08:13:39 -05:00 committed by Sean Owen
parent 96179732aa
commit 4cf81285da

View file

@ -1583,10 +1583,18 @@ be tolerated for stateful operations. You specify these thresholds using
``withWatermarks("eventTime", delay)`` on each of the input streams. For example, consider ``withWatermarks("eventTime", delay)`` on each of the input streams. For example, consider
a query with stream-stream joins between `inputStream1` and `inputStream2`. a query with stream-stream joins between `inputStream1` and `inputStream2`.
inputStream1.withWatermark("eventTime1", "1 hour") <div class="codetabs">
.join( <div data-lang="scala" markdown="1">
inputStream2.withWatermark("eventTime2", "2 hours"),
joinCondition) {% highlight scala %}
inputStream1.withWatermark("eventTime1", "1 hour")
.join(
inputStream2.withWatermark("eventTime2", "2 hours"),
joinCondition)
{% endhighlight %}
</div>
</div>
While executing the query, Structured Streaming individually tracks the maximum While executing the query, Structured Streaming individually tracks the maximum
event time seen in each input stream, calculates watermarks based on the corresponding delay, event time seen in each input stream, calculates watermarks based on the corresponding delay,