Mason Chen created FLINK-34445:
--
Summary: Integrate new endpoint with Flink UI metrics section
Key: FLINK-34445
URL: https://issues.apache.org/jira/browse/FLINK-34445
Project: Flink
Issue Type:
Mason Chen created FLINK-3:
--
Summary: Add new endpoint handler to flink
Key: FLINK-3
URL: https://issues.apache.org/jira/browse/FLINK-3
Project: Flink
Issue Type: Sub-task
Thanks Alex, added the clarification to the FLIP doc. It will return a kv
pairs of id to value following the conventions of other metric endpoints,
by extending `AbstractMetricsHandler`.
On Wed, Feb 14, 2024 at 9:38 AM Maximilian Michels wrote:
> No objections.
>
> -Max
>
> On Wed, Feb 14, 2024
No objections.
-Max
On Wed, Feb 14, 2024 at 1:49 PM Alexander Fedulov
wrote:
>
> Hi Mason,
>
> the adjustments of not requiring the operator ID make sense to me since
> this is the more prevalent expected usage pattern. I guess one small
> clarification that might be needed is the mention of
Hi Claire,
Thanks for reaching out. It's great that there is interest from Google
in spearheading the development of the respective Flink connectors.
As of now,there is only one GCP-specific connector developed directly as
part
of ASF Flink, namely the Pub/Sub one. It has already been
Hi Mason,
the adjustments of not requiring the operator ID make sense to me since
this is the more prevalent expected usage pattern. I guess one small
clarification that might be needed is the mention of the return data type.
I assume since there are potentially multiple coordinators that can
Matthias Pohl created FLINK-34443:
-
Summary:
YARNFileReplicationITCase.testPerJobModeWithCustomizedFileReplication failed
when deploying job cluster
Key: FLINK-34443
URL:
Hi!
Interesting catch. I think the current master branch behaviour is broken.
The chance to lose some records on `endInput`
is simply a critical bug. The limited buffer size is still problematic, as
it can surprise users. Having said that, the newly
proposed behaviour without any buffer is also
