You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/12/11 01:06:00 UTC

[jira] [Commented] (CALCITE-2033) Support followed by in pattern definition for MATCH_RECOGNIZE

    [ https://issues.apache.org/jira/browse/CALCITE-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285432#comment-16285432 ] 

Julian Hyde commented on CALCITE-2033:
--------------------------------------

[~dian.fu], [~ransom], Is there any progress on the reference implementation, CALCITE-1935? If the reference implementation is not ready yet, I think it would be sufficient to have some data tests. Then someone else could develop a reference implementation.

If you include a script with tests (CREATE TABLE, several INSERT statements, and SELECT statements with expected results) then I think that would be enough to go ahead and commit this PR. You could generate the data against Oracle 12.1 or higher.

> Support followed by in pattern definition for MATCH_RECOGNIZE
> -------------------------------------------------------------
>
>                 Key: CALCITE-2033
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2033
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Dian Fu
>            Assignee: Julian Hyde
>
> The [doc|https://docs.oracle.com/database/121/DWHSG/pattern.htm#DWHSG8986] has already defined pattern operator {{Concatenation}}. For example, pattern {{A B}} means that events matching pattern {{A}} and {{B}} should occur successively. There are also many use cases which require patterns to match events which not occur successively.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)