[
https://issues.apache.org/jira/browse/FLINK-13999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946393#comment-16946393
]
Dian Fu commented on FLINK-13999:
---------------------------------
[~dwysakowicz] Thanks for the confirmation and suggestion! The suggested
changes make sense to me. Regarding to the comment "change this value to have a
nicer average in the result", the price of "28" of the new row is good enough
for me given the average "14.0" is different from "14.5". Other good candidates
could be "22", "25", etc and the average will be "13.0", "13.5", etc. What do
you think?
> Correct the documentation of MATCH_RECOGNIZE
> --------------------------------------------
>
> Key: FLINK-13999
> URL: https://issues.apache.org/jira/browse/FLINK-13999
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: Dian Fu
> Priority: Major
>
> Regarding to the following
> [example|https://ci.apache.org/projects/flink/flink-docs-release-1.9/dev/table/streaming/match_recognize.html#aggregations]
> in the doc:
> {code:java}
> SELECT *
> FROM Ticker
> MATCH_RECOGNIZE (
> PARTITION BY symbol
> ORDER BY rowtime
> MEASURES
> FIRST(A.rowtime) AS start_tstamp,
> LAST(A.rowtime) AS end_tstamp,
> AVG(A.price) AS avgPrice
> ONE ROW PER MATCH
> AFTER MATCH SKIP TO FIRST B
> PATTERN (A+ B)
> DEFINE
> A AS AVG(A.price) < 15
> ) MR;
> {code}
> Given the inputs shown in the doc, it should be:
> {code:java}
> symbol start_tstamp end_tstamp avgPrice
> ========= ================== ================== ============
> ACME 01-APR-11 10:00:00 01-APR-11 10:00:03 14.5{code}
> instead of:
> {code:java}
> symbol start_tstamp end_tstamp avgPrice
> ========= ================== ================== ============
> ACME 01-APR-11 10:00:00 01-APR-11 10:00:03 14.5
> ACME 01-APR-11 10:00:04 01-APR-11 10:00:09 13.5
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
