Return-Path: <issues-return-114861-archive-asf-public=cust-asf.ponee.io@flink.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 12DC1200CA3
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Thu,  1 Jun 2017 15:29:24 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 11A26160BC4; Thu,  1 Jun 2017 13:29:24 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 55213160BB5
	for <archive-asf-public@cust-asf.ponee.io>; Thu,  1 Jun 2017 15:29:23 +0200 (CEST)
Received: (qmail 32312 invoked by uid 500); 1 Jun 2017 13:29:22 -0000
Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@flink.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@flink.apache.org>
List-Post: <mailto:issues@flink.apache.org>
List-Id: <issues.flink.apache.org>
Reply-To: dev@flink.apache.org
Delivered-To: mailing list issues@flink.apache.org
Received: (qmail 32303 invoked by uid 99); 1 Jun 2017 13:29:22 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jun 2017 13:29:22 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 32B95C1380
	for <issues@flink.apache.org>; Thu,  1 Jun 2017 13:29:22 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -4.02
X-Spam-Level: 
X-Spam-Status: No, score=-4.02 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024)
	with ESMTP id T_puo9lLPbEN for <issues@flink.apache.org>;
	Thu,  1 Jun 2017 13:29:21 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 283425FDEE
	for <issues@flink.incubator.apache.org>; Thu,  1 Jun 2017 13:29:17 +0000 (UTC)
Received: (qmail 31443 invoked by uid 99); 1 Jun 2017 13:29:17 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Jun 2017 13:29:17 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33)
	id E5A57E0885; Thu,  1 Jun 2017 13:29:16 +0000 (UTC)
From: dawidwys <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
References: <git-pr-4041-flink@git.apache.org>
In-Reply-To: <git-pr-4041-flink@git.apache.org>
Subject: [GitHub] flink pull request #4041: [FLINK-6198] [cep] Update CEP documentation.
Content-Type: text/plain
Message-Id: <20170601132916.E5A57E0885@git1-us-west.apache.org>
Date: Thu,  1 Jun 2017 13:29:16 +0000 (UTC)
archived-at: Thu, 01 Jun 2017 13:29:24 -0000

Github user dawidwys commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4041#discussion_r119610954
  
    --- Diff: docs/dev/libs/cep.md ---
    @@ -246,63 +333,118 @@ pattern.where(event => ... /* some condition */).or(event => ... /* or condition
     </div>
     </div>
     
    -Next, we can append further states to detect complex patterns.
    -We can control the contiguity of two succeeding events to be accepted by the pattern.
    +##### Conditions on Contiguity
    --- End diff --
    
    I would make it a higher level section and changed Conditions on Contiguity -> Contiguity.
    
    Also I think this is the place where inner contiguity for looping states should be described.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---