Github user twalthr commented on a diff in the pull request:
https://github.com/apache/flink/pull/2282#discussion_r73291620
--- Diff: docs/apis/table.md ---
@@ -606,6 +606,28 @@ Table result = in.orderBy("a.asc");
</td>
</tr>
+ <tr>
+ <td><strong>Offset</strong></td>
+ <td>
+ <p>Similar to a SQL OFFSET clause. Returns rows from offset
position. It is technically part of the ORDER BY clause.</p>
+{% highlight java %}
+Table in = tableEnv.fromDataSet(ds, "a, b, c");
+Table result = in.orderBy("a.asc").offset(3);
+{% endhighlight %}
+ </td>
+ </tr>
+
+ <tr>
+ <td><strong>Fetch</strong></td>
+ <td>
+ <p>Similar to a SQL FETCH clause. Returns a set number of rows.
FETCH canât be used by itself, it is used in conjunction with OFFSET.</p>
--- End diff --
IMO an immutable chain of `orderBy().offset().fetch()` is also not very
beautiful. I prefer `orderBy().limit()` as offset and fetch always belong
together. Maybe we need a third opinion here.
@aljoscha which syntax do you prefer?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
