MOBIN created FLINK-37860:
-
Summary: [paimon-connector]Fix Committer.createContext not passing
OperatorStateStore correctly
Key: FLINK-37860
URL: https://issues.apache.org/jira/browse/FLINK-37860
Project: Fli
I don't see a concern with this either.
The only thing I thought about is that the operator has a dependency to
Flink .. but since the JVM is backwards compatible, we will be able to
consume that Java 8 or Java 11 dependency with a JDK 17.
There are obviously Java language, JVM performance and ven
Hi folks. The invite link on
https://flink.apache.org/what-is-flink/community/#slack has expired. Can I get
an invite to the Slack group please?
Hello,
The invite link for Slack on this page
https://flink.apache.org/how-to-contribute/getting-help/ says expired.
Can you please send me an invite link for the Flink community on Slack?
Thanks,
Siva
Thank you for the feedback and guidance everyone :) I'll open a PR to drop
Python 3.8 support.
Kind regards,
Mika
Timo Walther created FLINK-37861:
Summary: FLIP-520: Simplify StructuredType handling
Key: FLINK-37861
URL: https://issues.apache.org/jira/browse/FLINK-37861
Project: Flink
Issue Type: New Fe
Hi Mayank,
Thanks for the response. I have a few more questions.
1. Why not use a catalog that has default properties? That way you could
re-use properties if the object exists in that catalog/database.
---
If we are insistent on Connections.
1. I don't understand the distinction between a "CO
Hi Ferenc,
+1 from my side on directional perspective.
Such job would be useful even for local python code testing (certain
changes break wheel packaging and testing all platforms are horror).
I've some questions/suggestions on the details though:
* I see it build macos-13, macos-14 but can't see
Timo Walther created FLINK-37862:
Summary: Implement data type improvements for StructuredType
Key: FLINK-37862
URL: https://issues.apache.org/jira/browse/FLINK-37862
Project: Flink
Issue Typ
+1 (binding)
We should still check whether changes to QueryOperationVisitor are
necessary but this is internal API and should not the FLIP. The public
API looks correct to me.
Cheers,
Timo
On 12.05.25 18:50, Hao Li wrote:
Hi everyone,
I'd like to start a vote on FLIP-526: Model ML_PREDICT
Hi Becket,
And thanks for the patch, Alan. I will also take a look at it this week.
> This is really something long wanted, as it simplifies the
> AsyncTableFunction calling syntax by so much.
I agree, I think it's a super useful feature that will make this
functionality much easier to use. Hap
Hi devs,
I've recently upgraded my Flink v1.20 apps using the FlinkKinesisConsumer
API to the newly recommended KinesisStreamsSource API. I'm now experiencing
that my Kinesis source operator (and hence, the entire application) can
stall in the initialising phase when restarting.
I've been able to
Hi Ferenc,
This should have already been supported. See FLINK-34487 [1] for more
details. I have checked the GHA nightly of the master branch and it
works well. The problem is that the backport PRs for release branchs
were not merged (which is not intended). I will follow up with the
backport PRs.
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.12.0
of Apache Flink Kubernetes Operator,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
**Release Overview**
As an overview, the release consists of t
Hi, Siva.
You can use this link[1] to join Flink community on Slack.
We will update the link on getting-help page later.
[1]
https://apache-flink.slack.com/join/shared_invite/zt-36qpbfpc0-wtlsC7lmeEUy5cw0VTHdag#/shared-invite/email
Siva Ram Gujju 于2025年5月29日周四 02:30写道：
> Hello,
>
> The invite
+1(binding)
Best,
Shengkai
Timo Walther 于2025年5月29日周四 00:00写道：
> +1 (binding)
>
> We should still check whether changes to QueryOperationVisitor are
> necessary but this is internal API and should not the FLIP. The public
> API looks correct to me.
>
> Cheers,
> Timo
>
>
> On 12.05.25 18:50, Ha
Hello devs,
I am in the process of creating the 1.19.3 and 1.20.2 patch releases, and
arriving to the step of preparing the PyFlink wheel files, I was surprised by
the fact that the suggested way is to use the Azure Pipeline [1], which points
to a deprecated doc on how to deploy a pipeline, etc. A
Solid +1 for dropping instead of deprecate.
Best,
Ferenc
On Wednesday, May 28th, 2025 at 07:12, Gabor Somogyi
wrote:
>
>
> Hi Mika,
>
> +1 to drop and not just deprecate from my side.
>
> BR,
> G
>
>
> On Wed, May 28, 2025 at 7:06 AM Dian Fu dian0511...@gmail.com wrote:
>
> > Hi Mika,
Joey Pereira created FLINK-37863:
Summary: DynamicKafkaSource support in PyFlink
Key: FLINK-37863
URL: https://issues.apache.org/jira/browse/FLINK-37863
Project: Flink
Issue Type: Improvement
Thanks all for the feedback on the FLIP. If there are no more discussions,
I will start voting on this tomorrow.
On Wed, May 21, 2025 at 6:00 AM Mayank Juneja
wrote:
> Hi Ryan,
>
> Thanks for the feedback.
>
> Just a quick clarification—DESCRIBE TABLE in Flink does *not* show table
> properties;
Joey Pereira created FLINK-37864:
Summary: Extend DynamicKafkaSource to allow for cluster-specific
OffsetsInitializer
Key: FLINK-37864
URL: https://issues.apache.org/jira/browse/FLINK-37864
Project:
Alan Sheinberg created FLINK-37865:
--
Summary: Add documentation for AsyncTableFunction
Key: FLINK-37865
URL: https://issues.apache.org/jira/browse/FLINK-37865
Project: Flink
Issue Type: Sub-
22 matches
Mail list logo
