Hi,
I notice that the latest version in olm of the operator is 1.5. I plan to run
the scripts to publish the 1.6 Flink operator to olm,
Kind regards, David.
Unless otherwise stated above:
IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO
a new class
ValueState2– that is used internally with the cleaned up Exceptions, but still
expose the old class and Exceptions for existing external applications. I guess
new applications could use the new ValueState2 .
What do you think?
Kind regards, David.
From: David Radley
Date
Hi ,
The argument seems to be that the errors cannot be acted on so should be
runtime exceptions. I want to confirm that none of these errors could / should
be retriable. If there is a possibility that the state is available at some
time later then I assume a checked retriable Exception would
on connector statuses. There’s already work being done to fix
the Flink Kafka connector. Any Flink connector comes after the new minor
version, similar to how it has been for all other connectors with Flink
1.17.
Best regards,
Martijn Visser
Op do 5 okt 2023 om 11:33 schreef David Radley
>
, those issues might need more time, we
should move forward with the Flink release without waiting for them. WDYT?
Best regards,
Jing
On Wed, Oct 4, 2023 at 6:15 PM David Radley wrote:
> Hi ,
> As release 1.18 removes the kafka connector from the core Flink
> repository, I assume we
Hi ,
As release 1.18 removes the kafka connector from the core Flink repository, I
assume we will wait until the kafka connector nightly build issues
https://issues.apache.org/jira/browse/FLINK-33104 and
https://issues.apache.org/jira/browse/FLINK-33017 are resolved before releasing
1.18?
Hi,
I was looking at the pr backlog in the Flink repository and realise that there
are 51 hits on the search
https://github.com/apache/flink/pulls?q=is%3Apr+is%3Aopen+kafka-connector.
And 25 hits on
ainstorming for ideas, and get the virtual circle that David
mentioned!
All my best, Ryan
On Wed, Oct 4, 2023 at 12:03 PM David Radley wrote:
>
> Hi,
> To add I agree with Martijn’s insights; I think we are saying similar things.
> To progress agreed upon work, and not blanket close al
Hi,
To add I agree with Martijn’s insights; I think we are saying similar things.
To progress agreed upon work, and not blanket close all stale prs,
Kind regards, David.
From: David Radley
Date: Wednesday, 4 October 2023 at 10:59
To: dev@flink.apache.org
Subject: [EXTERNAL] RE: Close
Hi ,
I agree Venkata this issue is bigger than closing out stale prs.
We can see that issues are being raised at a rate way above the resolution
time.
Hi,
I agree this is a standardising, simplifying change for read, simplifying
programmatically authoring the config file as well. As you know the mapping
for the old config form to the new form, could we write a migration tool, that
would convert the old config files to the new format, with
Hello,
I notice:
*the web UI listens on port 8081,
* The default port for that Flink listens on for rest calls is 8081.
* Specifying rest.port in the configuration changes the port for both
listeners.
We would like the 2 ports to be different so they can be secured differently,
Hi,
I re-opened https://issues.apache.org/jira/browse/FLINK-33159 . After it closed
as will not fix- l hopefully the words I have added reassure you that this is a
benign change – I intended this to just clean the build file by using
variables. I wanted to check this is ok with the community,
david radley created FLINK-33165:
Summary: Flink UI stack trace popup continually displayed when a
job is deleted
Key: FLINK-33165
URL: https://issues.apache.org/jira/browse/FLINK-33165
Project
david radley created FLINK-33159:
Summary: Use the variables for java and Maven version checks in
the pom file
Key: FLINK-33159
URL: https://issues.apache.org/jira/browse/FLINK-33159
Project: Flink
also to have this asset -> process ->
asset pattern for each of the steps in the job. If this is present, please
could you point me to it,
Kind regards, David.
From: David Radley
Date: Tuesday, 19 September 2023 at 16:11
To: dev@flink.apache.org
Subject: [EXTERNAL] RE: [DISCUSS]
Hi,
I notice that there is an experimental lineage integration for Flink with
OpenLineage https://openlineage.io/docs/integrations/flink . I think this
feature would allow for a superior Flink OpenLineage integration,
Kind regards, David.
From: XTransfer
Date: Tuesday, 19 September
Hi,
I like the proposal from Martijn. Having an ‘archived’ area for the older
material would make sense so users on the older versions can still access the
content for upgrade, keeping maybe the latest 3 releases in active table,
Kind regards, David.
From: Martijn Visser
Date: Friday, 15
:
[3.1.1,)
${target.java.version}
Is there a reason to have these 2 versions of Maven enforcers or can we use one
Maven enforcer that will apply to all cases?
Kind regards, David.
From: David Radley
Date: Friday, 15 September 2023 at 11:47
To: dev
Hi again,
I have just checked and you already enforcer have the enforcer for this in
master. I guess the only extra piece would be to put out a warning for java 8
indicating it is deprecated – I could look at that in a Jira,
Kind regards, David.
From: David Radley
Date: Friday, 15
.
so it depends on the Flink version
[1] https://lists.apache.org/thread/jbw3lzzoq5w16ckco3fc9xokycs3f22x
On Thu, Sep 14, 2023 at 4:09 PM David Radley
wrote:
> Hello,
> I am looking to build Flink from source I notice that the documentation
> https://nightlies.apache.org/flink/flink-doc
Hello,
I am looking to build Flink from source I notice that the documentation
https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/flinkdev/building/
says
https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/flinkdev/building/
In addition you need Maven 3 and a JDK (Java
101 - 122 of 122 matches
Mail list logo
