You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Zhiqiang He (JIRA)" <ji...@apache.org> on 2017/06/20 01:06:00 UTC
[jira] [Resolved] (CALCITE-1570) Add MATCH_RECOGNIZE operator, for
event pattern-matching
[ https://issues.apache.org/jira/browse/CALCITE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhiqiang He resolved CALCITE-1570.
----------------------------------
Resolution: Resolved
Fix Version/s: 1.13.0
> Add MATCH_RECOGNIZE operator, for event pattern-matching
> --------------------------------------------------------
>
> Key: CALCITE-1570
> URL: https://issues.apache.org/jira/browse/CALCITE-1570
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Zhiqiang He
> Fix For: 1.13.0
>
>
> Add the MATCH_RECOGNIZE operator, for event pattern-matching. Oracle [introduced this in 11i|https://oracle-base.com/articles/12c/pattern-matching-in-oracle-database-12cr1] (for tables) and Esper [implemented it|http://www.espertech.com/esper/release-5.1.0/esper-reference/html/match-recognize.html] (for streams of events).
> It would be most useful for streaming SQL but it makes sense in non-streaming SQL too (and of course it's good to be able to run streaming queries on historic data).
> Here is an example from [oracle-base|https://oracle-base.com/articles/12c/pattern-matching-in-oracle-database-12cr1]:
> {code}
> SELECT *
> FROM sales_history MATCH_RECOGNIZE (
> PARTITION BY product
> ORDER BY tstamp
> MEASURES STRT.tstamp AS start_tstamp,
> FINAL LAST(UP.tstamp) AS peak_tstamp,
> MATCH_NUMBER() AS mno,
> CLASSIFIER() AS cls
> ALL ROWS PER MATCH
> AFTER MATCH SKIP TO LAST DOWN
> PATTERN (STRT UP+ DOWN{1} UP+)
> DEFINE
> UP AS UP.units_sold > PREV(UP.units_sold),
> DOWN AS DOWN.units_sold < PREV(DOWN.units_sold)
> ) MR
> ORDER BY MR.product, MR.tstamp;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)