Is the intention to bump the Flink major version and only support Java 17+?
If so, can Scala not be upgraded at the same time?
Thanks,
Thomas
On Thu, Apr 27, 2023 at 4:53 PM Martijn Visser
wrote:
> Scala 2.12.7 doesn't compile on Java 17, see
> https://issues.apache.org/jira/browse/FLINK-25000
Hi Mason,
I added mason6345 to the Flink confluence space, you should be able to
add a FLIP now.
Looking forward to the contribution!
Thomas
On Thu, Jun 30, 2022 at 9:25 AM Martijn Visser wrote:
>
> Hi Mason,
>
> I'm sure there's a PMC (*hint*) out there who can grant you access to
> create a
One more question: Are you changing the parallelism when resuming from
savepoint?
On Sun, May 8, 2022 at 4:05 PM Thomas Weise wrote:
>
> Hi Kevin,
>
> Unfortunately I did not find a way to test the savepoint scenario with
> the MiniCluster. Savepoints are not supported in th
cible consistently? Can you
capture the debug log of the enumerator?
Thanks,
Thomas
On Wed, May 4, 2022 at 10:05 AM Martijn Visser wrote:
>
> Hi Kevin,
>
> I'm hoping that @Thomas Weise could help with the issue regarding the
> recovery from the savepoint.
>
> Best regards,
>
Thank you for reporting the issue. Mason has already identified the root
cause and the JIRA is now assigned to him:
https://issues.apache.org/jira/browse/FLINK-27479
Thomas
On Tue, May 3, 2022 at 4:02 AM Martijn Visser
wrote:
> I'm looping in @Thomas Weise since he has expertise
The Apache Flink community is very happy to announce the release of
Apache Flink 1.14.3, which is the second bugfix release for the Apache
Flink 1.14 series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data
streaming
Regarding session mode:
## Session Mode
* main() method executed in client
Session mode also supports execution of the main method on Jobmanager
with submission through REST API. That's how Flinkk k8s operators like
[1] work. It's actually an important capability because it allows for
allocation
;> integration advantages come from the active mode: being able to better
> >>> understand the job's resource requirements and adjust the deployment
> >>> resource accordingly. Both fine-grained resource management (customizing
> >>> TM
> >>> r
out-of the box
> experience with standalone mode on k8s, that makes the experience as close to
> running / operating any other application as possible.
>
> I'd really appreciate to hear your thoughts on this topic.
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-18
Hi,
I was recently looking at the Flink native Kubernetes integration [1]
to get an idea how it relates to existing operator based solutions
[2], [3].
Part of the native integration's motivations was simplicity (no extra
component to install), but arguably that is also a shortcoming. The
k8s oper
like a file and embed the writer schema in the
> state, so there is no need for an external registry. That should also work
> with dynamic queries. Only when you output messages into an event queue,
> you'd need the schema registry but that's orthogonal.
>
> On W
>> 2. The important thing here was that all your classes have to be
> >> "deployed" on every Task Manager/Job Manager in order to load them through
> >> DI.
> >> We achieved this by using what is called "Job session" cluster. Where our
> >> custom Fli
Hi,
I was looking into a problem that requires a configurable type
serializer for communication with a schema registry. The service
endpoint can change, so I would not want to make it part of the
serializer snapshot but rather resolve it at graph construction time
(similar to how a Kafka bootstrap
Thanks for making the release happen!
On Thu, Oct 21, 2021 at 5:54 AM Leonard Xu wrote:
>
> Thanks to Chesnay & Martijn and everyone who made this release happen.
>
>
> > 在 2021年10月21日，20:08，Martijn Visser 写道：
> >
> > Thank you Chesnay, Leonard and all contributors!
> >
> > On Thu, 21 Oct 2021 a
gt; releases
> >> > > of connectors, which are not bound to the release cycle of Flink
> >> itself.
> >> > I
> >> > > agree that in order to get there, we need to have stable interfaces
> >> which
> >> > > are trustwo
Thanks for initiating this discussion.
There are definitely a few things that are not optimal with our
current management of connectors. I would not necessarily characterize
it as a "mess" though. As the points raised so far show, it isn't easy
to find a solution that balances competing requiremen
docker plugin sounds good. I'll take a look at it.
> >
> > Regarding supporting JAVA 11:
> > - Not sure if it is necessary to ship JAVA. Maybe we could just change
> > the base image from openjdk:8-jre to openjdk:11-jre in template docker
> > file[1]. Correct me i
Thanks for working on improvements to the Flink Docker container images.
This will be important as more and more users are looking to adopt
Kubernetes and other deployment tooling that relies on Docker images.
A generic, dynamic configuration mechanism based on environment variables
is essential a
There is a related use case (not specific to HDFS) that I came across:
It would be nice if the jar upload endpoint could accept the URL of a jar
file as alternative to the jar file itself. Such URL could point to an
artifactory or distributed file system.
Thomas
On Mon, Nov 18, 2019 at 7:40 PM
from end to
> end by this Sunday. Then I'll update FLIP-27 wiki page.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
>
> On Sat, Nov 2, 2019 at 8:18 AM Thomas Weise wrote:
>
>> Is there any activity on FLIP-27 that would make it relevant for 1.10
>> release?
&
Is there any activity on FLIP-27 that would make it relevant for 1.10
release?
Thanks Gary for the update, it provides excellent visibility on current
activity and what we can expect with the release.
On Fri, Nov 1, 2019 at 1:52 PM Steven Wu wrote:
> Gary, FLIP-27 seems to get omitted in the
13, 2019 at 10:02 AM Shaoxuan Wang
> wrote:
>
> > Congratulations, Thomas!
> >
> > On Tue, Feb 12, 2019 at 5:59 PM Fabian Hueske
> wrote:
> >
> >> Hi everyone,
> >>
> >> On behalf of the Flink PMC I am happy to announce Thomas Weise as a new
+1 for trimming the size by default and offering the fat distribution as
alternative download
On Wed, Jan 23, 2019 at 8:35 AM Till Rohrmann wrote:
> Ufuk's proposal (having a lean default release and a user convenience
> tarball) sounds good to me. That way advanced users won't be bothered by a
The Apache Flink community is very happy to announce the release of Apache
Flink 1.5.6, which is the final bugfix release for the Apache Flink 1.5
series.
Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
app
24 matches
Mail list logo
