Seungchul Lee created FLINK-32128:
-
Summary: Unmodifiable implementation for getter method in test
function
Key: FLINK-32128
URL: https://issues.apache.org/jira/browse/FLINK-32128
Project: Flink
+1 (binding)
- Release notes look good
- Verified signatures and hashes
- Verified there are no binaries in the source archive
- Contents of the Maven repo look good
- Tag exists in Github
- Source archive build and unit tests pass
Thanks,
Danny
On Wed, May 10, 2023 at 4:58 PM Ryan Skraba
wrote
Hi Karthi,
Thanks for raising this proposal. It is a common use case to sink metric
"data" into downstream Prometheus. The description in the motivation
section is more or less misleading the discussion. I would suggest you
rephrase it, e.g. metrics (pre)processing via Flink is
The current F
Fang Yong created FLINK-32129:
-
Summary: Filesystem connector is not compatible with option
'pipeline.generic-types'
Key: FLINK-32129
URL: https://issues.apache.org/jira/browse/FLINK-32129
Project: Flink
Feifan Wang created FLINK-32130:
---
Summary: previous checkpoint will be broke by the subsequent
incremental checkpoint
Key: FLINK-32130
URL: https://issues.apache.org/jira/browse/FLINK-32130
Project: Fli
Dian Fu created FLINK-32131:
---
Summary: Support specifying hadoop config dir for Python
HiveCatalog
Key: FLINK-32131
URL: https://issues.apache.org/jira/browse/FLINK-32131
Project: Flink
Issue Type
+1 for the idea to introduce the prometheus connector.
In some cases, users cannot leverage the current way to report very large
amounts of metrics via metrics reporter due to the limit on the message
collection of prometheus agent.
For the FLIP itself, I think we should also consider the rate l
Hi Weijie,
just wondering how the process is going. Will the RC1 be released today?
Thanks for driving this!
Best regards,
Jing
On Wed, May 17, 2023 at 5:02 AM weijie guo
wrote:
> Hi Kevin,
>
> If everything goes smoothly, I will release the RC1 version of 1.17.1 this
> Thursday or Friday.
>
>
Hi Everyone,
In FLINK-31471, we've introduced new "in-place rescaling features" to the
Web UI that show up when the scheduler supports FLIP-291 REST endpoints.
I expect this to be a significant feature for user education (they have an
easy way to try out how rescaling behaves, especially in combi
