MarkSfik commented on a change in pull request #335:
URL: https://github.com/apache/flink-web/pull/335#discussion_r420036931
##########
File path:
_posts/2020-05-03-flink-sql-demo-building-e2e-streaming-application.md
##########
@@ -0,0 +1,338 @@
+---
+layout: post
+title: "Flink SQL Demo: Building an End-to-End Streaming Application"
+date: 2020-05-03T12:00:00.000Z
+categories: news
+authors:
+- jark:
+ name: "Jark Wu"
+ twitter: "JarkWu"
+excerpt: Apache Flink 1.10 has released many exciting new features, including
many developments in Flink SQL which is evolving at a fast pace. This article
takes a closer look at how to quickly build streaming applications with Flink
SQL from a practical point of view.
+---
+
+Apache Flink 1.10.0 has released many exciting new features, including many
developments in Flink SQL which is evolving at a fast pace. This article takes
a closer look at how to quickly build streaming applications with Flink SQL
from a practical point of view.
+
+In the following sections, we describe how to integrate Kafka, MySQL,
Elasticsearch, and Kibana with Flink SQL to analyze ecommerce user behavior in
real-time. All exercises in this article are performed in the Flink SQL CLI,
while the entire process uses plain SQL text, without a single line of Java or
Scala code or IDE installation. The final result of this demo is shown in the
following figure:
Review comment:
```suggestion
In the following sections, we describe how to integrate Kafka, MySQL,
Elasticsearch, and Kibana with Flink SQL to analyze e-commerce user behavior in
real-time. All exercises in this article are performed in the Flink SQL CLI,
while the entire process uses plain SQL text, without a single line of Java or
Scala code or IDE installation. The final result of this demo is shown in the
following figure:
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
