Yang Wang created FLINK-26815:
-
Summary: NullPointerException in FlinkConfigBuilderTest
Key: FLINK-26815
URL: https://issues.apache.org/jira/browse/FLINK-26815
Project: Flink
Issue Type: Bug
Thanks for the update Yun, and thanks all for the efforts! Look forward to
the first RC.
Best Regards,
Yu
On Tue, 22 Mar 2022 at 15:28, Yun Gao wrote:
> Hi Yu,
>
> Currently we still have some ongoing blocker issues tracked under [1].
>
> We are tighly tracking the progress of these issues and
Hi Ron,
Thanks for reviving the discussion of the work. The design looks good. A
small typo in the FLIP is that currently it is marked as released in 1.16.
Best Regards
Peter Huang
On Tue, Mar 22, 2022 at 10:58 PM Mang Zhang wrote:
> hi Yuxia,
>
>
> Thanks for your reply. Your reminder is ve
hi Yuxia,
Thanks for your reply. Your reminder is very important !
Since we download the file to the local, remember to clean it up when the flink
client exits
--
Best regards,
Mang Zhang
At 2022-03-23 10:02:26, "罗宇侠(莫辞)"
wrote:
>Hi Ron, Thanks for starting this dicuss, so
zhangjingcun created FLINK-26814:
Summary: Solve the problem that "should only have one jar" is
reported as an error when the application submits an operation in the yarn mode
Key: FLINK-26814
URL: https://issues.
Hi Ron, Thanks for starting this dicuss, some Spark/Hive users will benefit
from it. The flip looks good to me. I just have two minor questions:
1. For synax explanation, I see it's "Create function as identifier",
I think the word "identifier" may not be self-dedescriptive for actually
dalongliu created FLINK-26813:
-
Summary: Supports ADD/MODIFY column/watermark/constraint syntax
parse for ALTER TABLE
Key: FLINK-26813
URL: https://issues.apache.org/jira/browse/FLINK-26813
Project: Flink
Thomas Weise created FLINK-26812:
Summary: Flink native k8s integration should support owner
reference
Key: FLINK-26812
URL: https://issues.apache.org/jira/browse/FLINK-26812
Project: Flink
Thomas Weise created FLINK-26811:
Summary: Document CRD upgrade process
Key: FLINK-26811
URL: https://issues.apache.org/jira/browse/FLINK-26811
Project: Flink
Issue Type: Sub-task
jinfeng created FLINK-26810:
---
Summary: The local time zone does not take effect when the dynamic
index uses a field of type timestamp_ltz
Key: FLINK-26810
URL: https://issues.apache.org/jira/browse/FLINK-26810
Matthias Pohl created FLINK-26809:
-
Summary: ChangelogStorageMetricsTest.testAttemptsPerUpload failed
Key: FLINK-26809
URL: https://issues.apache.org/jira/browse/FLINK-26809
Project: Flink
Is
Luís Manuel Azevedo Costa created FLINK-26808:
-
Summary: [flink v1.14.2] Submit jobs via REST API not working
after set web.submit.enable: false
Key: FLINK-26808
URL: https://issues.apache.org/jira/bro
Hi everyone,
We’re very excited to announce our Call for Presentations for Flink
Forward San Francisco 2022! If you have an inspiring Apache Flink use
case, real-world application, or best practice, Flink Forward is the
platform for you to share your experiences.
https://www.flink-forward.or
Aitozi created FLINK-26807:
--
Summary: The batch job not work well with Operator
Key: FLINK-26807
URL: https://issues.apache.org/jira/browse/FLINK-26807
Project: Flink
Issue Type: Sub-task
Xin Hao created FLINK-26806:
---
Summary: Add deployment guide for Argo CD
Key: FLINK-26806
URL: https://issues.apache.org/jira/browse/FLINK-26806
Project: Flink
Issue Type: Improvement
Comp
No rush, but I just wanted to make sure this didn't fall through the
cracks. Thanks!
On Fri, Mar 18, 2022 at 4:43 PM Galen Warren
wrote:
> Currently, when the execution of a stateful function fails, the call is
> retried using an exponential backoff scheme -- the initial delay is 10ms
> (origina
Hi everyone,
I would like to discuss a particular aspect of our documentation: the
top-level structure with respect to languages and APIs. The current
structure is inconsistent and the direction is unclear to me, which makes
it hard for me to contribute gradual improvements.
Currently, the Python
Jingsong Lee created FLINK-26805:
Summary: Managed table breaks legacy connector without
'connector.type'
Key: FLINK-26805
URL: https://issues.apache.org/jira/browse/FLINK-26805
Project: Flink
> We should check there's no running Flink job before deleting a session
FlinkDeployment
If we have to prevent stopping the session cluster before all session jobs
are down already. I think we should avoid deleting the session deployment
by returning DeleteControl#noFinalizerRemoval()[1] in cleanu
Absolutely . Understood! We shall do.😊
-Original Message-
From: Chesnay Schepler
Sent: 22 March 2022 15:52
To: dev@flink.apache.org; Martijn Visser ; Marco
Zühlke
Cc: R, Aromal (GE Healthcare, consultant) ; Nellimarla, Aswini
(GE Healthcare)
Subject: EXT: Re: Flink cassandra connect
Márton Balassi created FLINK-26804:
--
Summary: Operator e2e tests sporadically fail: DEPLOYED_NOT_READY
Key: FLINK-26804
URL: https://issues.apache.org/jira/browse/FLINK-26804
Project: Flink
The relationship between the session deployment and the Flink jobs looks
good to me except for the session deployment deletion.
I strongly suggest not to set the ownerference of the FlinkSessionJob to
the session FlinkDeployment.
Otherwise, it will be a disaster if the session FlinkDeployment is d
I'd be quite curious on what the analysis that the mapper isn't re-used
is based on.
A given CassandraPojoSink instance has been re-using the same mapper
since it was added in 1.1:
https://github.com/apache/flink/blob/release-1.1/flink-streaming-connectors/flink-connector-cassandra/src/main/java
fanrui created FLINK-26803:
--
Summary: Merge small ChannelState file for Unaligned Checkpoint
Key: FLINK-26803
URL: https://issues.apache.org/jira/browse/FLINK-26803
Project: Flink
Issue Type: Improv
Thanks for fixing this!
Best,
Piotrek
pon., 21 mar 2022 o 18:21 Yun Gao napisał(a):
> Hi Piotr,
>
> Very thanks for the information and very sorry for the missing!
>
> Now I updated the flink.version property of the benchmark library
> and also update it to the checklist in the releasing introd
Hi Thomas:
Thanks for your valuable question. Let’s make the relationship between
the session deployment and the jobs more clear.
IMO, the session deployment and jobs interact in these situations:
- Create the session job. Then FlinkSessionJobController will wait for the
session cluster read
zhiyuan created FLINK-26802:
---
Summary: StreamPhysicalOverAggregate doesn't support consuming
update and delete changes which is produced by node Deduplicate
Key: FLINK-26802
URL: https://issues.apache.org/jira/browse/FL
Zhipeng Zhang created FLINK-26801:
-
Summary: LogisticRegressionTest.testGetModelData» Runtime Failed
to fetch next res...
Key: FLINK-26801
URL: https://issues.apache.org/jira/browse/FLINK-26801
Projec
Hi Jay,
Thanks for reaching out! As just mentioned in the ticket, the Cassandra
connector hasn't been actively maintained in the last couple months/years.
It would be great if there would be more contributors who could help out
with this. See also my previous request [1] on the Dev mailing list, w
YufeiLiu created FLINK-26800:
Summary: write small data file using share write buffer manager
Key: FLINK-26800
URL: https://issues.apache.org/jira/browse/FLINK-26800
Project: Flink
Issue Type: Bu
Feifan Wang created FLINK-26799:
---
Summary: StateChangeFormat#read not seek to offset correctly
Key: FLINK-26799
URL: https://issues.apache.org/jira/browse/FLINK-26799
Project: Flink
Issue Type:
Matthias Pohl created FLINK-26798:
-
Summary: JobMaster.testJobFailureWhenTaskExecutorHeartbeatTimeout
failed due to missing Execution
Key: FLINK-26798
URL: https://issues.apache.org/jira/browse/FLINK-26798
Yun Gao created FLINK-26797:
---
Summary:
ZKCheckpointIDCounterMultiServersTest.testRecoveredAfterConnectionLoss failed
on azure
Key: FLINK-26797
URL: https://issues.apache.org/jira/browse/FLINK-26797
Project
Hi Yu,
Currently we still have some ongoing blocker issues tracked under [1].
We are tighly tracking the progress of these issues and we'll start creating
the RC0 immediately after these blockers are solved, and hopefully inside
this week.
Best,
Yun Gao
[1]
https://issues.apache.org/jira/se
Thanks for the note Joe. Could you share with us the status of RC0
preparation and when it's planned to be created? Many thanks.
Best Regards,
Yu
On Tue, 22 Mar 2022 at 04:00, Johannes Moser wrote:
> Hello,
>
> As all relevant issues are assigned and worked on there’s no need to sync
> tomorro
Yun Gao created FLINK-26796:
---
Summary:
TaskManagerProcessFailureStreamingRecoveryITCase.testTaskManagerProcessFailure
failed on azure
Key: FLINK-26796
URL: https://issues.apache.org/jira/browse/FLINK-26796
Aitozi created FLINK-26795:
--
Summary: Fix the CI not fail fast after build failed
Key: FLINK-26795
URL: https://issues.apache.org/jira/browse/FLINK-26795
Project: Flink
Issue Type: Bug
Co
Yun Gao created FLINK-26794:
---
Summary: ChangelogRescalingITCase.test failed on azure due to
java.nio.file.NoSuchFileException
Key: FLINK-26794
URL: https://issues.apache.org/jira/browse/FLINK-26794
Project:
38 matches
Mail list logo
