Hi everyone,
we are currently in the process of setting up the flink-connectors repo [1]
for new connectors but we hit a wall that we currently cannot take:
branching model.
To reiterate the original motivation of the external connector repo: We
want to decouple the release cycle of a connector wi
Fangliang Liu created FLINK-24961:
-
Summary: When the DDL statement is different from the actual
schema in the database, ArrayIndexOutOfBoundsException will be reported
Key: FLINK-24961
URL: https://issues.apache
Dian Fu created FLINK-24962:
---
Summary: The root cause of a failed job was hidden in certain cases
Key: FLINK-24962
URL: https://issues.apache.org/jira/browse/FLINK-24962
Project: Flink
Issue Type:
Junfan Zhang created FLINK-24963:
Summary: Remove the tail separator when outputting yarn queue names
Key: FLINK-24963
URL: https://issues.apache.org/jira/browse/FLINK-24963
Project: Flink
Is
Maciej BryĆski created FLINK-24964:
--
Summary: Upgrade frontend-maven-plugin to 1.11.0
Key: FLINK-24964
URL: https://issues.apache.org/jira/browse/FLINK-24964
Project: Flink
Issue Type: Sub-t
Hi Arvid,
For branching model, the Pravega Flink connector has some experience what I
would like to share. Here[1][2] is the compatibility matrix and wiki explaining
the branching model and releases. Basically Pravega community aligns the
connector releases with the Pravega mainline release, an
Gen Luo created FLINK-24965:
---
Summary: Improper usage of Map.Entry after Entry Iterator.remove
in TaskLocaStateStoreImpl#pruneCheckpoints
Key: FLINK-24965
URL: https://issues.apache.org/jira/browse/FLINK-24965
Hi all,
tl;dr:
I think Timo pretty much said it all. As described in the issue, my
proposal is:
* Let's switch the default behavior of CAST to fail
* Let's add TRY_CAST to have the old behavior
* Let's add a rule (disabled by default) that wraps every CAST in a TRY, in
order to keep the old beha
hi, yun,
Thanks for the suggestion, but I am not sure whether we need such a prefix
or not, because the log has included vertex id, when the name is concise
enough, we can get the vertex id easily.
Does anyone have some comments on this?
Best,
Wenlong Lyu
On Thu, 18 Nov 2021 at 19:03, Yun Tang
Hi Stephan,
The discussion with you made me think more deeply about some things.
(3) Log Scan Startup mode.
> As I understand it, that means, though, that any managed table that uses
> another managed table as a source will automatically always use the "full
> scan" mode (snapshot + log subscr
jakevin created FLINK-24966:
---
Summary: Typo fix
Key: FLINK-24966
URL: https://issues.apache.org/jira/browse/FLINK-24966
Project: Flink
Issue Type: Improvement
Reporter: jakevin
Hi, I'
Hi Francesco,
Thanks for sharing your opinion about this and examples with other
programming
languages. I just want to mention, that NULL in SQL world is a bit
different with the
meaning in programming languages like java.
NULL in SQL essentially means "UNKNOWN", it's not as scary as a null in
ja
12 matches
Mail list logo