> There would be many different ways of doing this. One gateway per session
> cluster, one gateway shared across different clusters...
Currently, sql gateway cannot be shared across multiple clusters.
> understand the tradeoff and the simplest way of accomplishing this.
I'm not familiar with
Hi, Zhanghao
Thank you for proposing this FLIP, it is a very meaningful feature.
I agree that currently we may only consider the parallelism setting of the
source itself. If we consider the parallelism setting of other operators,
it may make the entire design more complex.
Regarding the
Hi ,
I've made updates to the FLIP[1] by incorporating relevant changes to avoid
using the Flink connector JDBC. This decision was based on the following
reasons:
AWS Redshift utilizes its specialized JDBC driver[2]. Given that their JDBC
driver may undergo evolutions over time, using the Flink
Hi Zhanghao,
Thanks for the explanation.
For Q1, I think the key lies in determining the boundary where the chain
should be broken. However, this boundary is ultimately determined by the
specific requirements of each user query.
The most straightforward approach is breaking the chain after the
Surendra Singh Lilhore created FLINK-33095:
--
Summary: Job jar related issue should be reported as BAD_REQUEST
instead of INTERNAL_SERVER_ERROR
Key: FLINK-33095
URL:
Hi Dong & Jinhao,
Thanks for your clarification! +1
Best regards,
Wencong
At 2023-09-15 11:26:16, "Dong Lin" wrote:
>Hi Wencong,
>
>Thanks for your comments! Please see my reply inline.
>
>On Thu, Sep 14, 2023 at 12:30 PM Wencong Liu wrote:
>
>> Dear Dong,
>>
>> I have
