[docs] rewrite tutorial doc for mysql-postgres-tutorial #514
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@wuchong , look forward your review, after that, I will also write a chinese version. |
luoyuxia
changed the title
luoyuxia
force-pushed
the
refine-tutorial-docs
branch
from
9656e0f
to
c98cc36
Compare
wuchong
reviewed
Oct 26, 2021
| 1. Download [Flink 1.13.2](https://downloads.apache.org/flink/flink-1.13.2/flink-1.13.2-bin-scala_2.11.tgz) and unzip it to the directory `flink-1.13.2` | ||
| 2. Download following JAR package required and put them under `flink-1.13.2/lib/`: | ||
|
|
||
| ```Download links are available only for stable releases.``` |
There was a problem hiding this comment.
Suggested change
| ```Download links are available only for stable releases.``` | |
| **Download links are available only for stable releases.** |
| ``` | ||
| We should see the welcome screen of the CLI client. | ||
|
|
||
|  |
There was a problem hiding this comment.
This image is not very clear, you can use this one: https://flink.apache.org/img/blog/2020-07-28-flink-sql-demo/image3.png
|
|
||
|  | ||
|
|
||
| Next, do some change in the databases, and then the enriched orders shown in Kibana will be updated after each step in reel time. |
There was a problem hiding this comment.
Suggested change
| Next, do some change in the databases, and then the enriched orders shown in Kibana will be updated after each step in reel time. | |
| Next, do some change in the databases, and then the enriched orders shown in Kibana will be updated after each step in real time. |
|
|
||
| ### Enriching the orders using the products and shipments tables and write to ElasticSearch |
There was a problem hiding this comment.
The title is a bit long, maybe we can simplify to Enriching orders and load to ElasticSearch.
| @@ -1,7 +1,22 @@ | |||
| # Streaming ETL from MySQL and Postgres to Elasticsearch | |||
| # Building a Streaming Application with Flink Mysql/Postgres CDC | |||
There was a problem hiding this comment.
Suggested change
| # Building a Streaming Application with Flink Mysql/Postgres CDC | |
| # Streaming ETL for MySQL and Postgres with Flink CDC |
|
|
||
| 1. Create `docker-compose.yml` file using following contents: | ||
| This tutorial is to show how to quickly build streaming applications with Flink Mysql/Postgres CDC. |
There was a problem hiding this comment.
Suggested change
| This tutorial is to show how to quickly build streaming applications with Flink Mysql/Postgres CDC. | |
| This tutorial is to show how to quickly build streaming ETL for MySQL and Postgres with Flink CDC. |
| Assuming we are running an e-commerce business. The product and order data stored in MySQL, the shipment data related to the order is stored in Postgres. | ||
| We need to build a streaming application to meet the following requirements: | ||
| 1. Enrich the orders using the product and shipment table and write enriched orders to ElasticSearch in real time | ||
| 2. Calculate the GMV(Gross Merchandise Volume) by daily and write to Kafka in real time |
There was a problem hiding this comment.
I think we can remove the GMV demo to make the blog focus on streaming join.
wuchong
reviewed
Oct 26, 2021
| @@ -174,7 +152,7 @@ docker-compose down | |||
| (default,10002,'Hangzhou','Shanghai',false), | |||
| (default,10003,'Shanghai','Hangzhou',false); | |||
| ``` | |||
| ## Launching the Streaming Application | |||
| ## Launching the Streaming ETL | |||
There was a problem hiding this comment.
We can remove this 2nd header and make all the 3rd headers to be 2nd level. This sub-title doesn't provide much information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current mysql-postgres-tutorial is quite not intuitively, so I rewrite the tutorial to make it intuitively.