Skip to content

Commit 9f6a423

Browse files
authored
Add info about creating tables in confluent cloud (#1641)
1 parent 6ccea2b commit 9f6a423

File tree

10 files changed

+20
-0
lines changed

10 files changed

+20
-0
lines changed
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
NOTE: Confluent Cloud manages several options for you when using Flink SQL. So, if you run this tutorial on Confluent Cloud, you can copy just the `CREATE TABLE` statements without the `WITH` clause when creating tables.

_includes/tutorials/aggregating-count/flinksql/markup/dev/create-movie-ticket-sales.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,6 @@ Note that we are defining the schema for the table, which includes three fields:
66
+++++
77
<pre class="snippet"><code class="sql">{% include_raw tutorials/aggregating-count/flinksql/code/tutorial-steps/dev/create-movie-ticket-sales.sql %}</code></pre>
88
+++++
9+
10+
11+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/aggregating-minmax/flinksql/markup/dev/create-movie-sales.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,5 @@ Note that we are defining the schema for the table, which includes four fields:
66
+++++
77
<pre class="snippet"><code class="sql">{% include_raw tutorials/aggregating-minmax/flinksql/code/tutorial-steps/dev/create-movie-sales.sql %}</code></pre>
88
+++++
9+
10+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/cumulating-windows/flinksql/markup/dev/create-orders.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,5 @@ but for other scenarios, a delayed watermark strategy may be more appropriate. T
99
+++++
1010
<pre class="snippet"><code class="sql">{% include_raw tutorials/cumulating-windows/flinksql/code/tutorial-steps/dev/create-orders.sql %}</code></pre>
1111
+++++
12+
13+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/filtering/flinksql/markup/dev/create-all-publications.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,5 @@ Note that we are defining the schema for the table, which includes four fields:
66
+++++
77
<pre class="snippet"><code class="sql">{% include_raw tutorials/filtering/flinksql/code/tutorial-steps/dev/create-all-publications.sql %}</code></pre>
88
+++++
9+
10+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/finding-distinct/flinksql/markup/dev/create-clicks-table.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,5 @@ First, you'll need to create a table to represent click events from users. Noti
55
+++++
66

77
Note that we are using the field `clicks_ts_raw` as the record's timestamp. This is going to be important later on when we write a query to deduplicate these events and knowing when each event occurred is important.
8+
9+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/hopping-windows/flinksql/markup/dev/create-temperature-readings.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,5 @@ but for other scenarios, a delayed watermark strategy may be more appropriate. T
99
+++++
1010
<pre class="snippet"><code class="sql">{% include_raw tutorials/hopping-windows/flinksql/code/tutorial-steps/dev/create-temperature-readings.sql %}</code></pre>
1111
+++++
12+
13+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/joining-stream-stream/flinksql/markup/dev/create-orders-table.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,3 +5,5 @@ First, you'll need to create a table to represent the orders:
55
+++++
66

77
Note that we are using the field `order_ts_raw` as the record's timestamp. This is going to be important later on when we write queries that need to know about the time each event occurred at. By using a field of the event, we can process the events at any time and get a deterministic result. This is known as _event time_.
8+
9+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/splitting/flinksql/markup/dev/create-acting-events.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,3 +4,5 @@ Note that we are defining the schema for the table, which includes three fields:
44
+++++
55
<pre class="snippet"><code class="sql">{% include_raw tutorials/splitting/flinksql/code/tutorial-steps/dev/create-acting-events.sql %}</code></pre>
66
+++++
7+
8+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

_includes/tutorials/tumbling-windows/flinksql/markup/dev/create-ratings.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,5 @@ but for other scenarios, a delayed watermark strategy may be more appropriate. T
99
+++++
1010
<pre class="snippet"><code class="sql">{% include_raw tutorials/tumbling-windows/flinksql/code/tutorial-steps/dev/create-ratings.sql %}</code></pre>
1111
+++++
12+
13+
{% include shared/markup/dev/flink_sql_cloud_with.adoc %}

0 commit comments

Comments
 (0)