Flink SQL tumbling windows tutorial (#1625)

* feat: add Flink SQL tumbling windows tutorial

* chore: wording tweaks and typos fixes

These are largely copy/paste issues noticed during tumbling windows tutorial dev.

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

Co-authored-by: Bill Bejeck <bbejeck@gmail.com>

---------

Co-authored-by: Bill Bejeck <bbejeck@gmail.com>

Author: davetroiano

.semaphore/semaphore.yml

@@ -499,6 +499,9 @@ blocks:
     - name: Flink SQL test for filtering
       commands:
       - make -C _includes/tutorials/filtering/flinksql/code tutorial
+    - name: Flink SQL tumbling windows tests
+      commands:
+      - make -C _includes/tutorials/tumbling-windows/flinksql/code tutorial
     - name: Flink SQL test for deduplication
       commands:
       - make -C _includes/tutorials/finding-distinct/flinksql/code tutorial

_data/harnesses/tumbling-windows/flinksql.yml

@@ -0,0 +1,146 @@
+dev:
+  steps:
+    - title: Prerequisites
+      content:
+        - action: skip
+          render:
+            file: shared/markup/dev/docker-prerequisite.adoc
+
+    - title: Initialize the project
+      content:
+        - action: execute
+          file: tutorial-steps/dev/init.sh
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/dev/init.adoc
+
+    - title: Get Confluent Platform
+      content:
+        - action: make_file
+          file: docker-compose.yml
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/dev/make-docker-compose.adoc
+
+        - action: execute_async
+          file: tutorial-steps/dev/docker-compose-up.sh
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/dev/start-compose.adoc
+
+        - action: execute
+          file: tutorial-steps/dev/wait-for-containers.sh
+          render:
+            skip: true
+
+    - title: Write the program interactively using the CLI
+      content:
+        - action: docker_flinksql_cli_session
+          container: flink-sql-client
+          docker_bootup_file: tutorial-steps/dev/start-cli.sh
+          column_width: 20
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/dev/start-cli.adoc
+          stdin:
+            - file: tutorial-steps/dev/create-ratings.sql
+              render:
+                file: tutorials/tumbling-windows/flinksql/markup/dev/create-ratings.adoc
+
+            - file: tutorial-steps/dev/populate-ratings.sql
+              render:
+                file: tutorials/tumbling-windows/flinksql/markup/dev/populate-ratings.adoc
+
+            - file: tutorial-steps/dev/transient-query-ratings-by-6hr-window.sql
+              render:
+                file: tutorials/tumbling-windows/flinksql/markup/dev/transient-query-ratings-by-6hr-window.adoc
+
+            - file: tutorial-steps/dev/create-ratings-by-6hr-window.sql
+              render:
+                file: tutorials/tumbling-windows/flinksql/markup/dev/create-ratings-by-6hr-window.adoc
+
+          stdout:
+            directory: tutorial-steps/dev/outputs
+
+    - title: Validate output
+      content:
+        - action: execute
+          file: tutorial-steps/dev/validate-ratings-by-6hr-window.sh
+          stdout: tutorial-steps/dev/outputs/validate-ratings-by-6hr-window.log
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/dev/validate-ratings-by-6hr-window.adoc
+
+test:
+  steps:
+    - title: Decide what testing tools to use
+      content:
+        - action: skip
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/test-architecture.adoc
+
+    - title: Create the test skeleton
+      content:
+        - action: execute
+          file: tutorial-steps/test/make-test-dirs.sh
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/make-test-dirs.adoc
+
+        - action: make_file
+          file: build.gradle
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/make-build-gradle.adoc
+
+        - action: execute
+          file: tutorial-steps/test/gradle-wrapper.sh
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/make-gradle-wrapper.adoc
+
+    - title: Create SQL resources
+      content:
+        - action: make_file
+          file: src/test/resources/create-ratings.sql.template
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/create-resource-create-ratings.sql.template.adoc
+
+        - action: make_file
+          file: src/test/resources/populate-ratings.sql
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/create-resource-populate-ratings.sql.adoc
+
+        - action: make_file
+          file: src/test/resources/create-ratings-by-6hr-window.sql.template
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/create-resource-create-ratings-by-6hr-window.sql.template.adoc
+
+        - action: make_file
+          file: src/test/resources/query-ratings-by-6hr-window.sql
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/create-resource-query-ratings-by-6hr-window.sql.adoc
+
+        - action: make_file
+          file: src/test/resources/expected-ratings-by-6hr-window.txt
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/create-resource-expected-ratings-by-6hr-window.txt.adoc
+
+    - title: Write a test
+      content:
+        - action: make_file
+          file: src/test/java/io/confluent/developer/AbstractFlinkKafkaTest.java
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/make-test-base.adoc
+
+        - action: make_file
+          file: src/test/java/io/confluent/developer/FlinkSqlTumblingWindowTest.java
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/make-test.adoc
+
+    - title: Invoke the test
+      content:
+        - action: execute
+          file: tutorial-steps/test/invoke-test.sh
+          render:
+            file: tutorials/tumbling-windows/flinksql/markup/test/invoke-test.adoc
+
+ccloud:
+  steps:
+    - title: Run your app to Confluent Cloud
+      content:
+        - action: skip
+          render:
+            file: shared/markup/ccloud/try-ccloud.adoc

_data/tutorials.yaml

@@ -165,6 +165,7 @@ tumbling-windows:
     ksql: enabled
     kstreams: enabled
     confluent: enabled
+    flinksql: enabled
 hopping-windows:
   title: How to create hopping windows
   meta-description: create hopping windows for time-series events

_includes/shared/markup/ccloud/try-ccloud-properties.adoc

@@ -1,6 +1,6 @@
-Instead of running a local Kafka cluster, you may use https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully-managed Apache Kafka service.
+Instead of running a local Kafka cluster, you may use https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully managed Apache Kafka service.
 
-1. Sign up for https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully-managed Apache Kafka service.
+1. Sign up for https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully managed Apache Kafka service.
   
 2. After you log in to Confluent Cloud Console, click on `Add cloud environment` and name the environment `learn-kafka`. Using a new environment keeps your learning resources separate from your other Confluent Cloud resources.
 

_includes/shared/markup/ccloud/try-ccloud.adoc

@@ -1,6 +1,6 @@
-Instead of running a local Kafka cluster, you may use https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully-managed Apache Kafka service.
+Instead of running a local Kafka cluster, you may use https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully managed Apache Kafka service.
 
-1. Sign up for https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully-managed Apache Kafka service.
+1. Sign up for https://www.confluent.io/confluent-cloud/tryfree/[Confluent Cloud], a fully managed Apache Kafka service.
   
 2. After you log in to Confluent Cloud Console, click on `Add cloud environment` and name the environment `learn-kafka`. Using a new environment keeps your learning resources separate from your other Confluent Cloud resources.
 

_includes/tutorials/aggregating-count/flinksql/markup/dev/transient-query.adoc

@@ -14,7 +14,7 @@ This should yield the following output:
 
 Enter `Q` to return to the Flink SQL prompt.
 
-Note that these results were materialized in memory and printed in a human readable table representation because the default `sql-client.execution.result-mode` configuration value is `table`. You can view non-materialized streaming results as a changelog by running `SET 'sql-client.execution.result-mode' = 'changelog';`
+Note that these results were materialized in memory and printed in a human-readable table representation because the default `sql-client.execution.result-mode` configuration value is `'table'`. You can view non-materialized streaming results as a changelog by running `SET 'sql-client.execution.result-mode' = 'changelog';`
 and rerunning the same query. The results will look like this:
 
 +++++

_includes/tutorials/aggregating-count/flinksql/markup/test/create-resource-create-movie-sales.sql.template.adoc

@@ -2,7 +2,7 @@ We could always inline the SQL statements in our Java test code, but creating se
 
 There are a handful of resources to create for our test. These mirror the queries that we developed earlier.
 
-Create the following file at `src/test/resources/create-movie-sales.sql.template`. Note the `KAFKA_PORT` and `SCHEMA_REGISTRY_PORT` placeholders in this file. Out test will dynamically assign these to the ports that Testcontainers assigns.
+Create the following file at `src/test/resources/create-movie-sales.sql.template`. Note the `KAFKA_PORT` and `SCHEMA_REGISTRY_PORT` placeholders in this file. Our test will dynamically assign these to the ports that Testcontainers assigns.
 
 +++++
 <pre class="snippet"><code class="groovy">{% include_raw tutorials/aggregating-count/flinksql/code/src/test/resources/create-movie-sales.sql.template %}</code></pre>

_includes/tutorials/aggregating-count/flinksql/markup/test/test-architecture.adoc

@@ -5,11 +5,11 @@ automated testing are clear, but how do we get there?
 
 First, what do we want in an automated integration test? For starters:
 
-. *Real running services* that our application depends on
+. *Real services* (as opposed to mock) that our application depends on
 . *Small resource footprint* so that developers can run the test locally
 . *Low enough latency* so that development iterations aren't hampered -- not as low latency as is required for a unit test, but test duration should be on the order of seconds
 . *Isolation* so that many tests can run concurrently on the same machine when this test gets run on a build automation server, e.g., no hardcoded ports
 
 Luckily, tools are at our disposal to solve these problems. We'll use https://www.testcontainers.org/[Testcontainers] to run
 containerized Kafka and Schema Registry servers on dynamic ports, Flink's support for local execution environments so that we don't need to spin up a Flink cluster, and Flink's Table API
-in order to execute the Flink SQL statements that comprise our application.
+to execute the Flink SQL statements that comprise our application.

_includes/tutorials/aggregating-minmax/flinksql/markup/dev/transient-query.adoc

@@ -14,7 +14,7 @@ This should yield the following output:
 
 Enter `Q` to return to the Flink SQL prompt.
 
-Note that these results were materialized in memory and printed in a human readable table representation because the default `sql-client.execution.result-mode` configuration value is `table`. You can view non-materialized streaming results as a changelog by running `SET 'sql-client.execution.result-mode' = 'changelog';`
+Note that these results were materialized in memory and printed in a human-readable table representation because the default `sql-client.execution.result-mode` configuration value is `'table'`. You can view non-materialized streaming results as a changelog by running `SET 'sql-client.execution.result-mode' = 'changelog';`
 and rerunning the same query. The results will look like this:
 
 +++++

_includes/tutorials/aggregating-minmax/flinksql/markup/test/create-resource-create-movie-sales.sql.template.adoc

@@ -2,7 +2,7 @@ We could always inline the SQL statements in our Java test code, but creating se
 
 There are a handful of resources to create for our test. These mirror the queries that we developed earlier.
 
-Create the following file at `src/test/resources/create-movie-sales.sql.template`. Note the `KAFKA_PORT` and `SCHEMA_REGISTRY_PORT` placeholders in this file. Out test will dynamically assign these to the ports that Testcontainers assigns.
+Create the following file at `src/test/resources/create-movie-sales.sql.template`. Note the `KAFKA_PORT` and `SCHEMA_REGISTRY_PORT` placeholders in this file. Our test will dynamically assign these to the ports that Testcontainers assigns.
 
 +++++
 <pre class="snippet"><code class="groovy">{% include_raw tutorials/aggregating-minmax/flinksql/code/src/test/resources/create-movie-sales.sql.template %}</code></pre>