[
https://issues.apache.org/jira/browse/FLINK-23270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375359#comment-17375359
]
Fangliang Liu commented on FLINK-23270:
---------------------------------------
[~jark]
it is same as INNER Equi-JOIN when adding JOIN ON condition. Returns a simple
Cartesian product restricted by the join condition.Does not meet the
description "For example, if there is a new record on the left side, it will be
joined with all the previous and future records on the right side." in Regular
Joins section.
In addition, this example is the same as INNER Equi-JOIN section.
> The examples in the documentation are inappropriate
> ---------------------------------------------------
>
> Key: FLINK-23270
> URL: https://issues.apache.org/jira/browse/FLINK-23270
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Table SQL / API
> Reporter: Fangliang Liu
> Priority: Major
>
> [https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/table/sql/queries/joins/]
> Regular Joins description
> Regular joins are the most generic type of join in which any new record, or
> changes to either side of the join, are visible and affect the entirety of
> the join result. For example, if there is a new record on the left side, it
> will be joined with all the previous and future records on the right side.
> But, example
> {code:java}
> SELECT * FROM Orders
> INNER JOIN Product
> ON Orders.productId = Product.id
> {code}
> Is the following better?
> {code:java}
> SELECT * FROM Orders
> INNER JOIN Product
> {code}
> [~jark] , looking forward to your replay.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
