Hi,
Flink SQL follows the standard SQL, so I think SQL syntax will be richer
and richer in higher versions, it will not be changed.
Best,
Ron
liu ron 于2023年4月13日周四 10:24写道：
> Hi,
> Flink SQL follows the standard SQL, so I think SQL syntax will be richer
> and richer in higher versions, it will
Hi
Currently, Calcite supports standard SQL, so I think the main SQL syntax
will remain unchanged or backward compatible even when Flink upgrades its
calcite version. You can refer to it.
Best,
Shammon FY
On Tue, Apr 11, 2023 at 12:00 PM ravi_suryavanshi.yahoo.com via user <
Hi,we have decided to use the Table API using Flink SQL syntax (NOT JAVA). Can
SQL syntax be changed in the higher version?as per the doc "SQL support is
based on Apache Calcite which implements the SQL standard."
Thanks & Regards,RaviOn Saturday, 25 March, 2023 at 06:21:49 pm IST, Mate
Thanks a lot Hand and Mate
On Saturday, 25 March, 2023 at 06:21:49 pm IST, Mate Czagany
wrote:
Hi,
Please also keep in mind that restoring existing Table API jobs from savepoints
when upgrading to a newer minor version of Flink, e.g. 1.16 -> 1.17 is not
supported as the topology
Hi,
Please also keep in mind that restoring existing Table API jobs from
savepoints when upgrading to a newer minor version of Flink, e.g. 1.16 ->
1.17 is not supported as the topology might change between these versions
due to optimizer changes.
See here for more information:
Hi,
I think the SQL job is better. Flink SQL jobs can be easily shared with
others for debugging. And it is more suitable for flow batch integration.
For a small part of jobs which can not be expressed through SQL, we will
choose a job by DataStream API.
Best,
Hang
ravi_suryavanshi.yahoo.com
Hello Team,Need your advice on which method is recommended considering don't
want to change my query code when the Flink is updated/upgraded to the higher
version.
Here I am seeking advice for writing the SQL using java code(Table API
function and Expression) or using pure SQL.
I am assuming
