You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by sj...@apache.org on 2020/09/09 14:24:50 UTC
[flink-web] branch asf-site updated (02395fa -> 4190204)
This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git.
from 02395fa [hotfix] Introduced new parameter to enable futures during build.
add 1df9af1 [hotfix] add links to Advanced Application Patterns Vol. 3
new 4190204 rebuild site
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
_posts/2020-01-15-demo-fraud-detection.md | 2 +-
_posts/2020-03-24-demo-fraud-detection-2.md | 2 +-
content/README.md | 0
content/blog/feed.xml | 4 ++--
content/news/2020/01/15/demo-fraud-detection.html | 2 +-
content/news/2020/03/24/demo-fraud-detection-2.html | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
delete mode 100644 content/README.md
[flink-web] 01/01: rebuild site
Posted by sj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 41902044cfd1896f3570eea1bc0b687212ebb5af
Author: Seth Wiesman <sj...@gmail.com>
AuthorDate: Wed Sep 9 09:24:27 2020 -0500
rebuild site
---
content/README.md | 0
content/blog/feed.xml | 4 ++--
content/news/2020/01/15/demo-fraud-detection.html | 2 +-
content/news/2020/03/24/demo-fraud-detection-2.html | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/README.md b/content/README.md
deleted file mode 100644
index e69de29..0000000
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 5eb2a75..eb21205 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -5986,7 +5986,7 @@ There are actually a few more specialized data partitioning schemes in Flink whi
<p>In the above code, <code>processElement()</code> receives Transactions, and <code>processBroadcastElement()</code> receives Rule updates. When a new rule is created, it is distributed as depicted in Figure 6 and saved in all parallel instances of the operator using <code>processBroadcastState</code>. We use a Rule’s ID as the key to store and reference individual rules. Instead of iterating over a hardcoded <code>List&lt;Rules&gt [...]
-<p><code>DynamicAlertFunction</code> follows the same logic with respect to storing the rules in the broadcast <code>MapState</code>. As described in <a href="https://flink.apache.org/news/2020/01/15/demo-fraud-detection.html">Part 1</a>, each message in the <code>processElement</code> input is intended to be processed by one specific rule and comes “pre-marked” with a corresponding ID by <code>DynamicKeyFunction</ [...]
+<p><code>DynamicAlertFunction</code> follows the same logic with respect to storing the rules in the broadcast <code>MapState</code>. As described in <a href="https://flink.apache.org/news/2020/01/15/demo-fraud-detection.html">Part 1</a>, each message in the <code>processElement</code> input is intended to be processed by one specific rule and comes “pre-marked” with a corresponding ID by <code>DynamicKeyFunction</ [...]
<h1 id="summary">Summary</h1>
@@ -7262,7 +7262,7 @@ However, you need to take care of another aspect, which is providing timestamps
<ul>
<li><a href="/news/2020/03/24/demo-fraud-detection-2.html">Dynamic updates of application logic</a></li>
<li>Dynamic data partitioning (shuffle), controlled at runtime</li>
- <li>Low latency alerting based on custom windowing logic (without using the window API)</li>
+ <li><a href="/news/2020/07/30/demo-fraud-detection-3.html">Low latency alerting</a> based on custom windowing logic (without using the window API)</li>
</ul>
<p>These patterns expand the possibilities of what is achievable with statically defined data flows and provide the building blocks to fulfill complex business requirements.</p>
diff --git a/content/news/2020/01/15/demo-fraud-detection.html b/content/news/2020/01/15/demo-fraud-detection.html
index dcb51b4..4c6bba3 100644
--- a/content/news/2020/01/15/demo-fraud-detection.html
+++ b/content/news/2020/01/15/demo-fraud-detection.html
@@ -202,7 +202,7 @@
<ul>
<li><a href="/news/2020/03/24/demo-fraud-detection-2.html">Dynamic updates of application logic</a></li>
<li>Dynamic data partitioning (shuffle), controlled at runtime</li>
- <li>Low latency alerting based on custom windowing logic (without using the window API)</li>
+ <li><a href="/news/2020/07/30/demo-fraud-detection-3.html">Low latency alerting</a> based on custom windowing logic (without using the window API)</li>
</ul>
<p>These patterns expand the possibilities of what is achievable with statically defined data flows and provide the building blocks to fulfill complex business requirements.</p>
diff --git a/content/news/2020/03/24/demo-fraud-detection-2.html b/content/news/2020/03/24/demo-fraud-detection-2.html
index 463e3f4..8ec7629 100644
--- a/content/news/2020/03/24/demo-fraud-detection-2.html
+++ b/content/news/2020/03/24/demo-fraud-detection-2.html
@@ -379,7 +379,7 @@ There are actually a few more specialized data partitioning schemes in Flink whi
<p>In the above code, <code>processElement()</code> receives Transactions, and <code>processBroadcastElement()</code> receives Rule updates. When a new rule is created, it is distributed as depicted in Figure 6 and saved in all parallel instances of the operator using <code>processBroadcastState</code>. We use a Rule’s ID as the key to store and reference individual rules. Instead of iterating over a hardcoded <code>List<Rules></code>, we iterate over entries in the dynamically-upd [...]
-<p><code>DynamicAlertFunction</code> follows the same logic with respect to storing the rules in the broadcast <code>MapState</code>. As described in <a href="https://flink.apache.org/news/2020/01/15/demo-fraud-detection.html">Part 1</a>, each message in the <code>processElement</code> input is intended to be processed by one specific rule and comes “pre-marked” with a corresponding ID by <code>DynamicKeyFunction</code>. All we need to do is retrieve the definition of the corresponding [...]
+<p><code>DynamicAlertFunction</code> follows the same logic with respect to storing the rules in the broadcast <code>MapState</code>. As described in <a href="https://flink.apache.org/news/2020/01/15/demo-fraud-detection.html">Part 1</a>, each message in the <code>processElement</code> input is intended to be processed by one specific rule and comes “pre-marked” with a corresponding ID by <code>DynamicKeyFunction</code>. All we need to do is retrieve the definition of the corresponding [...]
<h1 id="summary">Summary</h1>