Sorry I forgot to add the version information, the version is 1.17
刘峻池 于2023年11月20日周一 13:59写道：
> Hi Flink Community
>
> When I run this command `flink run-application -t yarn-application -sae
> mainClass somejar` to submit some batch-task on YARN with Application
> Mode, my shell client always
Hi Flink Community
When I run this command `flink run-application -t yarn-application -sae
mainClass somejar` to submit some batch-task on YARN with Application
Mode, my shell client always terminates after task submission success,
then the dispatcher cannot receive the client heartbeat for a lon
Hi Jing,
Thank you for your feedback. I understand your concerns regarding putting
all methods into the RuntimeContext flat.
I would like to share some of my thoughts on this matter.
Firstly, this FLIP only proposes the addition of three additional methods,
which should not impose too much extra
Hi David and Mason,
Thanks for your feedback!
To David:
> Given that the new default feels more complex than the current behavior,
if we decide to do this I think it will be important to include the
rationale you've shared in the documentation.
Sounds make sense to me, I will add the related do
Hi, julia.
I have read the code about this part. The problem as you said is that the
RowType passed to the avro-confluent format is nullable, which will cause
union with null in the schema.
I think FLINK-30438 is the same problem as yours. But I find the RowType
passed to avro-confluent format in
Hi Junrui,
Thanks for bringing this to our attention. First of all, it makes sense to
deprecate RuntimeContext#getExecutionConfig.
Afaic, this is an issue of how we design API with clean concepts/aspects.
There are two issues mentioned in the FLIP:
1. short of user-facing abstraction - we just e
