Caizhi Weng created FLINK-25242:
---
Summary: UDF with primitive int argument does not accept int
values even after a not null filter
Key: FLINK-25242
URL: https://issues.apache.org/jira/browse/FLINK-25242
Ingo Bürk created FLINK-25241:
-
Summary: Architectural tests do not fail on CI if violations are
removed
Key: FLINK-25241
URL: https://issues.apache.org/jira/browse/FLINK-25241
Project: Flink
Is
Ada Wong created FLINK-25240:
Summary: Update log4j2 version to 2.15.0
Key: FLINK-25240
URL: https://issues.apache.org/jira/browse/FLINK-25240
Project: Flink
Issue Type: Bug
Components
Hi, Timo, thanks for updating the doc.
I have a comment on plan migration:
I think we may need to add a version field for every exec node when
serialising. In earlier discussions, I think we have a conclusion that
treating the version of plan as the version of node, but in this case it
would be br
Ada Wong created FLINK-25239:
Summary: Delete useless variables
Key: FLINK-25239
URL: https://issues.apache.org/jira/browse/FLINK-25239
Project: Flink
Issue Type: Improvement
Components
+1 for repo per connector from my side also
Thanks for trying out the different approaches.
Where would the common/infra pieces live? In a separate repository
with its own release?
Thomas
On Thu, Dec 9, 2021 at 12:42 PM Till Rohrmann wrote:
>
> Sorry if I was a bit unclear. +1 for the single r
Praneeth Ramesh created FLINK-25238:
---
Summary: flink iceberg source reading array types fail with Cast
Exception
Key: FLINK-25238
URL: https://issues.apache.org/jira/browse/FLINK-25238
Project: Flin
Yun Tang created FLINK-25237:
Summary: ElasticsearchSinkITCase fails due to
NoNodeAvailableException
Key: FLINK-25237
URL: https://issues.apache.org/jira/browse/FLINK-25237
Project: Flink
Issue
Sorry if I was a bit unclear. +1 for the single repo per connector approach.
Cheers,
Till
On Thu, Dec 9, 2021 at 5:41 PM Till Rohrmann wrote:
> +1 for the single repo approach.
>
> Cheers,
> Till
>
> On Thu, Dec 9, 2021 at 3:54 PM Martijn Visser
> wrote:
>
>> I also agree that it feels more na
Ben Augarten created FLINK-25236:
Summary: Add a mechanism to generate and validate a jobgraph with
a checkpoint before submission
Key: FLINK-25236
URL: https://issues.apache.org/jira/browse/FLINK-25236
+1 for the single repo approach.
Cheers,
Till
On Thu, Dec 9, 2021 at 3:54 PM Martijn Visser wrote:
> I also agree that it feels more natural to go with a repo for each
> individual connector. Each repository can be made available at
> flink-packages.org so users can find them, next to referring
+1, agreed with Seth's reasoning. There has been no real activity in MapR
FS module for years [1], so the eventual users should be good with using
the jars from the older Flink versions for quite some time
[1]
https://github.com/apache/flink/commits/master/flink-filesystems/flink-mapr-fs
Best,
D.
Hi Martijn, I've just opened a backport PR [1] for FLINK-23946 [2].
[1] https://github.com/apache/flink/pull/18066
[2] https://issues.apache.org/jira/browse/FLINK-23946
Best,
D.
On Thu, Dec 9, 2021 at 4:59 PM Fabian Paul wrote:
> Actually I meant https://issues.apache.org/jira/browse/FLINK-251
Actually I meant https://issues.apache.org/jira/browse/FLINK-25126
sorry for the confusion.
On Thu, Dec 9, 2021 at 4:55 PM Fabian Paul wrote:
>
> Hi Martijn,
>
> I just opened the backport for
> https://issues.apache.org/jira/browse/FLINK-25132. The changes are
> already approved I only wait for
Hi Martijn,
I just opened the backport for
https://issues.apache.org/jira/browse/FLINK-25132. The changes are
already approved I only wait for a green Azure build.
Best,
Fabian
On Thu, Dec 9, 2021 at 4:01 PM Martijn Visser wrote:
>
> Hi all,
>
> Thanks for the fixes Jingsong and Zhu!
>
> That m
+1 (what Seth said)
On Thu, Dec 9, 2021 at 4:15 PM Seth Wiesman wrote:
> +1
>
> I actually thought we had already dropped this FS. If anyone is still
> relying on it in production, the file system abstraction in Flink has been
> incredibly stable over the years. They should be able to use the 1.
+1
I actually thought we had already dropped this FS. If anyone is still
relying on it in production, the file system abstraction in Flink has been
incredibly stable over the years. They should be able to use the 1.14 MapR
FS with later versions of Flink.
Seth
On Wed, Dec 8, 2021 at 10:03 AM Mar
Hi all,
Thanks for the fixes Jingsong and Zhu!
That means that we still have the following tickets open:
* https://issues.apache.org/jira/browse/FLINK-23946 - Application mode
fails fatally when being shut down -> A PR is there, just pending a review.
* https://issues.apache.org/jira/browse/FLIN
I also agree that it feels more natural to go with a repo for each
individual connector. Each repository can be made available at
flink-packages.org so users can find them, next to referring to them in
documentation. +1 from my side.
On Thu, 9 Dec 2021 at 15:38, Arvid Heise wrote:
> Hi all,
>
>
Hi everyone,
thanks for the healthy discussion. Let us find a compromise to make all
parties happy.
> NULL in SQL essentially means "UNKNOWN"
This argument is true, but as a user I would like to know the `Why?` a
value is UNKNOWN. I could imagine users have spent hours on finding the
root c
David Morávek created FLINK-25235:
-
Summary: Re-enable
ZooKeeperLeaderElectionITCase#testJobExecutionOnClusterWithLeaderChange
Key: FLINK-25235
URL: https://issues.apache.org/jira/browse/FLINK-25235
P
Hi all,
We tried out Chesnay's proposal and went with Option 2. Unfortunately, we
experienced tough nuts to crack and feel like we hit a dead end:
- The main pain point with the outlined Frankensteinian connector repo is
how to handle shared code / infra code. If we have it in some
branch, then w
Egor Ryashin created FLINK-25234:
Summary: Flink should parse ISO timestamp in UTC format
Key: FLINK-25234
URL: https://issues.apache.org/jira/browse/FLINK-25234
Project: Flink
Issue Type: Im
Hi Jing and Godfrey,
I had another iteration over the document. There are two major changes:
1. Supported Flink Upgrade Versions
I got the feedback via various channels that a step size of one minor
version is not very convenient. As you said, "because upgrading to a new
version is a time-con
Till Rohrmann created FLINK-25233:
-
Summary: UpsertKafkaTableITCase.testAggregate fails on AZP
Key: FLINK-25233
URL: https://issues.apache.org/jira/browse/FLINK-25233
Project: Flink
Issue Typ
ZhuoYu Chen created FLINK-25232:
---
Summary: flink sql supports fine-grained state configuration
Key: FLINK-25232
URL: https://issues.apache.org/jira/browse/FLINK-25232
Project: Flink
Issue Type:
Hi everyone,
I'm happy to announce that we have unanimously approved this FLIP.
There are 5 approving votes, 4 of which are binding:
Till Rohrmann (binding)
Xintong Song (binding)
Yang Wang (non-binding)
Zhu Zhu (binding)
Matthias Pohl (binding)
There are no disapproving votes. Thanks everyone
Dian Fu created FLINK-25231:
---
Summary: Update PyFlink to use the new type system
Key: FLINK-25231
URL: https://issues.apache.org/jira/browse/FLINK-25231
Project: Flink
Issue Type: Improvement
Timo Walther created FLINK-25230:
Summary: Harden type serialization in JSON plan
Key: FLINK-25230
URL: https://issues.apache.org/jira/browse/FLINK-25230
Project: Flink
Issue Type: Sub-task
Francesco Guardiani created FLINK-25229:
---
Summary: Introduce flink-table-api-bridge-common
Key: FLINK-25229
URL: https://issues.apache.org/jira/browse/FLINK-25229
Project: Flink
Issue T
Francesco Guardiani created FLINK-25228:
---
Summary: Introduce flink-table-test-utils
Key: FLINK-25228
URL: https://issues.apache.org/jira/browse/FLINK-25228
Project: Flink
Issue Type: Bu
31 matches
Mail list logo
