[jira] [Created] (FLINK-8568) flink table's guava classes can't beed relocated by maven-shed-plugin.

John Fang created FLINK-8568: Summary: flink table's guava classes can't beed relocated by maven-shed-plugin. Key: FLINK-8568 URL: https://issues.apache.org/jira/browse/FLINK-8568 Proj

[jira] [Created] (FLINK-8567) Maven-shade-plugin can't relocate Scala classes.

John Fang created FLINK-8567: Summary: Maven-shade-plugin can't relocate Scala classes. Key: FLINK-8567 URL: https://issues.apache.org/jira/browse/FLINK-8567 Project: Flink Issue Type

[jira] [Created] (FLINK-7833) Flink's Literal(value, SqlTimeTypeInfo) fails to convert Calctie's RexNode

John Fang created FLINK-7833: Summary: Flink's Literal(value, SqlTimeTypeInfo) fails to convert Calctie's RexNode Key: FLINK-7833 URL: https://issues.apache.org/jira/browse/FLINK-7833 Proj

Re: the Table API `limit` is confused

limit(offset, fetch). > I'll also create a PR for the issue very soon; PR reviews are welcome. > > The requirement for orderBy() exists to ensure that queries are > deterministic. > > Best, Fabian > > > 2017-10-12 8:39 GMT+02:00 John Fang : > > > Now the Tabl

Re: the Table API `limit` is confused

Now the Table don't support the limit operator without orderBy operator. On Thu, Oct 12, 2017 at 2:30 PM, John Fang wrote: > Hi, > >In order to support ORDER BY OFFSET FETCH, we add the Table API > `limit`. But the api is confused. For example: "table.limit(3)"

the Table API `limit` is confused

refer to use the API "offset().fetch()" support ORDER BY OFFSET FETCH. Of course, the "table.limit(n)" equivalent with the "table.offset(0).fetch(n)", -- Regards John Fang