[kafka] branch trunk updated: KAFKA-8208: Change paper link directly to ASM (#6572)

[bb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bbejeck pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 312e55b  KAFKA-8208: Change paper link directly to ASM (#6572)
312e55b is described below

commit 312e55bf56c4670f0a2701b94dc21bfc8fa2990d
Author: Bill Bejeck <bb...@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 79f5b82..1e1aeb7 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>