[ https://issues.apache.org/jira/browse/CALCITE-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021504#comment-16021504 ]
Julian Hyde commented on CALCITE-1645: -------------------------------------- Finished review, testing now. I renamed your {{enum AfterMatchOption}} to {{RowsPerMatchOption}}. Your name just didn't make sense. I see you haven't added any tests to SqlToRelConverterTest yet. Next commit, can you please add a test there. Then you'll notice that the {{Match.explainTerms}} method is way out of date. :) > Row per match syntax support for MATCH_RECOGNIZE > ------------------------------------------------- > > Key: CALCITE-1645 > URL: https://issues.apache.org/jira/browse/CALCITE-1645 > Project: Calcite > Issue Type: Sub-task > Components: core > Affects Versions: 1.11.0 > Reporter: Zhiqiang He > Assignee: Zhiqiang He > Labels: features > > h1. [ONE ROW | ALL ROWS] PER MATCH: Choosing Summaries or Details for Each > Match > You will sometimes want summary data about the matches and other times need > details. You can do that with the following SQL: > * ONE ROW PER MATCH > Each match produces one summary row. This is the default. > * ALL ROWS PER MATCH > A match spanning multiple rows will produce one output row for each row in > the match. > The output is explained in "Row Pattern Output". > The MATCH_RECOGNIZE clause may find a match with zero rows. For an empty > match, ONE ROW PER MATCH returns a summary row: the PARTITION BY columns take > the values from the row where the empty match occurs, and the measure columns > are evaluated over an empty set of rows. > ALL ROWS PER MATCH has three suboptions: > * ALL ROWS PER MATCH SHOW EMPTY MATCHES > * ALL ROWS PER MATCH OMIT EMPTY MATCHES > * ALL ROWS PER MATCH WITH UNMATCHED ROWS -- This message was sent by Atlassian JIRA (v6.3.15#6346)