providerType config and idle source (#7274)

Co-authored-by: ZbyszekMM <[email protected]>
TouK · Dec 3, 2024 · 5a4bbe5 · 5a4bbe5
1 parent 6f09c83
commit 5a4bbe5
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/docs/configuration/model/ModelConfiguration.md b/docs/configuration/model/ModelConfiguration.md
@@ -54,12 +54,12 @@ Below you can see typical component configuration, each section describes config
 ```
   components {
     sqlHsql {
-      providerType: sql
+      providerType: databaseEnricher
       jdbcUrl: jdbc:hsql...//
       admin/pass
     }
     sqlOracle {
-      providerType: sql
+      providerType: databaseEnricher
       jdbcUrl: jdbc:oracle...//
       admin/pass
     }

diff --git a/docs/scenarios_authoring/AggregatesInTimeWindows.md b/docs/scenarios_authoring/AggregatesInTimeWindows.md
@@ -14,6 +14,9 @@ Nussknacker implements 3 types of time windows - tumbling, sliding and session w
 
 Regardless of the window type used, events are grouped into windows based on the event time. Therefore, it is important to understand where Nussknacker takes information about event time from, can event time info be accessed from SpEL and so on - you can find more info [here](../scenarios_authoring/DataSourcesAndSinks.md#notion-of-time--flink-engine-only).
 
+Finally, understanding watermarks and problems caused by idle sources will clarify why in certain situations aggregate events or results of joins are not generated. A good description of the problem can be found [here](https://medium.com/@ipolyzos_/understanding-watermarks-in-apache-flink-c8793a50fbb8).
+
+
 
 ## Common behavior
Original file line number	Diff line number	Diff line change
Expand Up		@@ -14,6 +14,9 @@ Nussknacker implements 3 types of time windows - tumbling, sliding and session w

		Regardless of the window type used, events are grouped into windows based on the event time. Therefore, it is important to understand where Nussknacker takes information about event time from, can event time info be accessed from SpEL and so on - you can find more info [here](../scenarios_authoring/DataSourcesAndSinks.md#notion-of-time--flink-engine-only).

		Finally, understanding watermarks and problems caused by idle sources will clarify why in certain situations aggregate events or results of joins are not generated. A good description of the problem can be found [here](https://medium.com/@ipolyzos_/understanding-watermarks-in-apache-flink-c8793a50fbb8).



		## Common behavior

Expand Down