wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362368088
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -587,61 +587,61 @@ WHERE o.id = s.orderId AND
o.ordertime BETWEEN s.shiptime - INTERVAL '4' HOUR AND s.shiptime
{% endhighlight %}
-The example above will join all orders with their corresponding shipments if
the order was shipped four hours after the order was received.
+以上示例中,所有在收到后四小时内发货的 order 会与他们相关的 shipment 进行 join。
</td>
</tr>
<tr>
- <td>
+ <td>
<strong>Expanding arrays into a relation</strong><br>
- <span class="label label-primary">Batch</span> <span class="label
label-primary">Streaming</span>
+ <span class="label label-primary">批处理</span> <span class="label
label-primary">流处理</span>
</td>
- <td>
- <p>Unnesting WITH ORDINALITY is not supported yet.</p>
+ <td>
+ <p>目前尚未支持非嵌套的 WITH ORDINALITY 。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders CROSS JOIN UNNEST(tags) AS t (tag)
{% endhighlight %}
</td>
</tr>
<tr>
- <td>
- <strong>Join with Table Function (UDTF)</strong><br>
- <span class="label label-primary">Batch</span> <span class="label
label-primary">Streaming</span>
+ <td>
+ <strong>Join 表函数 (UDTF)</strong><br>
+ <span class="label label-primary">批处理</span> <span class="label
label-primary">流处理</span>
</td>
- <td>
- <p>Joins a table with the results of a table function. Each row of the
left (outer) table is joined with all rows produced by the corresponding call
of the table function.</p>
- <p>User-defined table functions (UDTFs) must be registered before. See
the <a href="{{ site.baseurl }}/dev/table/functions/udfs.html">UDF
documentation</a> for details on how to specify and register UDTFs. </p>
+ <td>
+ <p>将表与表函数的结果进行 join 操作。左表(outer)中的每一行将会与调用表函数所产生的所有结果中相关联行进行 join 。</p>
+ <p>用户自定义表函数( User-defined table functions,UDTFs ) 在执行前必须先注册。请参考 <a
href="{{ site.baseurl }}/zh/dev/table/functions/udfs.html">UDF 文档</a>
以获取更多关于指定和注册UDF的信息 </p>
<p><b>Inner Join</b></p>
- <p>A row of the left (outer) table is dropped, if its table function
call returns an empty result.</p>
+ <p>若表函数返回了空结果,左表(outer)的行将会被删除。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders, LATERAL TABLE(unnest_udtf(tags)) t AS tag
{% endhighlight %}
<p><b>Left Outer Join</b></p>
- <p>If a table function call returns an empty result, the corresponding
outer row is preserved and the result padded with null values.</p>
+ <p>若表函数返回了空结果,将会保留相对应的外部行并用空值填充结果。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) t AS tag ON TRUE
{% endhighlight %}
- <p><b>Note:</b> Currently, only literal <code>TRUE</code> is supported
as predicate for a left outer join against a lateral table.</p>
+ <p><b>注意:</b> 当前仅支持文本常量 <code>TRUE</code> 作为针对横向表的左外部联接的谓词。</p>
</td>
</tr>
<tr>
<td>
- <strong>Join with Temporal Table Function</strong><br>
- <span class="label label-primary">Streaming</span>
+ <strong>Join Temporal Tables 函数</strong><br>
+ <span class="label label-primary">流处理</span>
</td>
<td>
- <p><a href="{{ site.baseurl
}}/dev/table/streaming/temporal_tables.html">Temporal tables</a> are tables
that track changes over time.</p>
- <p>A <a href="{{ site.baseurl
}}/dev/table/streaming/temporal_tables.html#temporal-table-functions">Temporal
table function</a> provides access to the state of a temporal table at a
specific point in time.
- The syntax to join a table with a temporal table function is the same
as in <i>Join with Table Function</i>.</p>
+ <p><a href="{{ site.baseurl
}}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a>
是跟随时间变化而变化的表。</p>
+ <p><a href="{{ site.baseurl
}}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions">
Temporal Tables 函数( Temporal table function )</a> 提供访问 Temporal Tables
在某一时间点的状态的能力。
Review comment:
```suggestion
<p><a href="{{ site.baseurl
}}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions">
Temporal Table Function</a> 提供访问 Temporal Tables 在某一时间点的状态的能力。
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services