Hi Devs,
I would like to start a discussion on FLIP-363: Unify the Representation of
TaskManager Location in REST API and Web UI [1].
The TaskManager location of subtasks is important for identifying TM-related
problems. There are a number of places in REST API and Web UI where TaskManager
loc
Elphas Toringepi created FLINK-33068:
Summary: Handle DNS errors in AWS connectors as recoverable
Key: FLINK-33068
URL: https://issues.apache.org/jira/browse/FLINK-33068
Project: Flink
Is
Hi devs,
While I was joining the flink-avro enhancement and cleanup discussion
driven by Becket[1], I realized that there are some issues with the current
Flink API annotation usage in the source code.
As far as I am concerned, Flink wants to control the access/visibility of
APIs across modules a
Thanks for driving this FLIP, Allison.
+1 (non-binding
Regards
Venkata krishnan
On Thu, Sep 7, 2023 at 1:20 PM Allison Chang
wrote:
> Hi everyone,
>
> Would like to start the VOTE for FLIP-323<
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/FLINK/FLIP-323*3A*Support
Thanks for the description. Will try to hack it around :)
G
On Thu, Sep 7, 2023 at 4:56 PM Matthias Pohl
wrote:
> You should be able to adapt tools/azure-pipelines/build-apache-repo.yml [1]
> in your branch as a "debug" commit to add the steps/stages that you're
> planning to include in a test
Hi Matthias!
Thank you for the detailed proposal, overall I am in favor of making this
unification to simplify the logic and make the integration for external
components more straightforward.
I will try to read through the proposal more carefully next week and
provide some detailed feedback.
+1
Hi everyone,
Please review [1] and vote on the release candidate #1 for the version
3.3.0 of Apache Flink Stateful Functions,
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
Hi Jark and Leonard,
Thanks for the comments. Please see my reply below.
@Jark
> I think a better API doesn't compete with itself. Therefore, I'm in favor of
> supporting the watermark lag threshold for each source without introducing
> any framework API and configuration.
I don't think support
Gyula Fora created FLINK-33067:
--
Summary: Expose JODK rate limiter config and enable by default
Key: FLINK-33067
URL: https://issues.apache.org/jira/browse/FLINK-33067
Project: Flink
Issue Type:
dongwoo.kim created FLINK-33066:
---
Summary: Enable to inject environment variable from
secret/configmap to operatorPod
Key: FLINK-33066
URL: https://issues.apache.org/jira/browse/FLINK-33066
Project: Fli
Rui Fan created FLINK-33065:
---
Summary: Optimize the exception message when the program plan
could not be fetched
Key: FLINK-33065
URL: https://issues.apache.org/jira/browse/FLINK-33065
Project: Flink
11 matches
Mail list logo