This is an automated email from the ASF dual-hosted git repository.
bbejeck pushed a commit to branch 2.2
in repository https://gitbox.apache.org/repos/asf/kafka.git
The following commit(s) were added to refs/heads/2.2 by this push:
new b73c077 KAFKA-8208: Change paper link directly to ASM (#6572)
b73c077 is described below
commit b73c07759f8325f20ca6d7df232b4a6b4acbba9b
Author: Bill Bejeck <bbej...@gmail.com>
AuthorDate: Sat Apr 13 18:59:40 2019 -0400
KAFKA-8208: Change paper link directly to ASM (#6572)
Reviewers: Matthias J. Sax <mj...@apache.org>, Victoria Bialas
<vi...@confluent.io>
---
docs/streams/core-concepts.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index c925c2e..391167d 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -224,7 +224,7 @@
<p>
Besides the guarantee that each record will be processed exactly-once,
another issue that many stream processing application will face is how to
- handle <a
href="https://www.confluent.io/wp-content/uploads/streams-tables-two-sides-same-coin.pdf";>out-of-order
data</a> that may impact their business logic. In Kafka Streams, there are two
causes that could potentially
+ handle <a
href="https://dl.acm.org/citation.cfm?id=3242155";>out-of-order data</a> that
may impact their business logic. In Kafka Streams, there are two causes that
could potentially
result in out-of-order data arrivals with respect to their timestamps:
</p>
