Re: [DISCUSS] Improve Flink logging with contextual information

+1 to Rong’s approach. Using java option and log4j, we could save the user logs to different file. Best Yang Gyula Fóra 于2019年10月18日周五 下午4:41写道： > Hi all! > > Thanks for the answers, this has been very helpful and we could set up a > similar scheme using the Env variables. > > Cheers, > Gyula

Re: [DISCUSS] FLIP-72: Introduce Pulsar Connector

Hi everyone, Glad to receive your valuable feedbacks. I'd first separate the Pulsar catalog as another doc and show more design and implementation details there. For the current FLIP-72, I would separate it into the sink part for current work and keep the source part as future works until we

[jira] [Created] (FLINK-14471) Hide error message when metric api failed

Yadong Xie created FLINK-14471: -- Summary: Hide error message when metric api failed Key: FLINK-14471 URL: https://issues.apache.org/jira/browse/FLINK-14471 Project: Flink Issue Type: Sub-task

Re: Watermarks not propagated to WebUI?

The issue persists with 1.9.1: https://issues.apache.org/jira/browse/FLINK-14470 On Mon, Aug 26, 2019 at 1:47 AM Jan Lukavský wrote: > Hi Robert, > > I'd very much love to, but because I run my pipeline with Beam, I'm > afraid I will have to wait a little longer, before Beam has runner for >

Re: [ANNOUNCE] Apache Flink 1.9.1 released

Filed as https://issues.apache.org/jira/browse/FLINK-14470 On Sun, Oct 20, 2019 at 7:09 PM Yadong Xie wrote: > Hi Thomas Weise > > We have an issue related to this problem > https://issues.apache.org/jira/browse/FLINK-14147, but I think you could > open another JIRA > The watermark data comes

Re: [VOTE] FLINK-67: Cluster partition life-cycle

Thanks Chesnay for proposing this improvement! It's meaningful for interactive query and the design looks good. +1 (non-binding) Thanks, Zhu Zhu Till Rohrmann 于2019年10月17日周四 下午8:48写道： > Thanks for creating this FLIP and starting the VOTE for it. > > +1 (binding) > > Cheers, > Till > > On Thu,

[jira] [Created] (FLINK-14470) Watermark display not working with high parallelism job

Thomas Weise created FLINK-14470: Summary: Watermark display not working with high parallelism job Key: FLINK-14470 URL: https://issues.apache.org/jira/browse/FLINK-14470 Project: Flink

Re: [DISCUSS] FLIP-67: Global partitions lifecycle

Thanks Till for the explanation! That looks good to me. Thanks, Zhu Zhu Till Rohrmann 于2019年10月21日周一 上午2:45写道： > Hi Zhu Zhu, > > the cluster partition does not need to be registered at the RM before it > can be used. The cluster partition descriptor will be reported to the > client as part of

[jira] [Created] (FLINK-14469) Drop Python 2 support

Dian Fu created FLINK-14469: --- Summary: Drop Python 2 support Key: FLINK-14469 URL: https://issues.apache.org/jira/browse/FLINK-14469 Project: Flink Issue Type: Task Components: API /

Re: [ANNOUNCE] Apache Flink 1.9.1 released

Hi Thomas Weise We have an issue related to this problem https://issues.apache.org/jira/browse/FLINK-14147, but I think you could open another JIRA The watermark data comes from metric REST API, which is too heavy for high parallelism jobs, the API almost sure will break when the parallelism is

Re: [SURVEY] Dropping non Credit-based Flow Control

+1 Credit-based flow control has long been used in our production environment as well. It works fine and there seems no reason to use non credit-based implementation. Regards, Xiaogang Zhu Zhu 于2019年10月19日周六 下午3:01写道： > +1 to drop the non credit-based flow control. > We have turned to

Re: [DISCUSS] FLIP-67: Global partitions lifecycle

Hi Zhu Zhu, the cluster partition does not need to be registered at the RM before it can be used. The cluster partition descriptor will be reported to the client as part of the job execution result. This information is used to construct a JobGraph which can consume from a cluster partition. The

[ANNOUNCE] Weekly Community Update 2019/42

Dear community, happy to share this week's community update with the release of Flink 1.9.1, a couple of threads about our development process, the sql ecosystem and more. Flink Development == * [releases] *Apache Flink 1.9.1* was released. [1,2] * [statefun] Stephan has started a

Re: [ANNOUNCE] Apache Flink 1.9.1 released

Thanks Jark and everyone who contributed to the release! I took 1.9.1 for a test drive, upgrading an existing 1.8.x deployment. This brought in the shiny new UI :) Everything looks good so far, except an error message that is flickering on the job overview page: "Server response message: unable

[jira] [Created] (FLINK-14468) Update Kubernetes docs

Maximilian Bode created FLINK-14468: --- Summary: Update Kubernetes docs Key: FLINK-14468 URL: https://issues.apache.org/jira/browse/FLINK-14468 Project: Flink Issue Type: Task

[jira] [Created] (FLINK-14467) Let MesosJobClusterEntrypoint use user code class loader

Guowei Ma created FLINK-14467: - Summary: Let MesosJobClusterEntrypoint use user code class loader Key: FLINK-14467 URL: https://issues.apache.org/jira/browse/FLINK-14467 Project: Flink Issue

[jira] [Created] (FLINK-14466) Let YarnJobClusterEntrypoint use user code class loader

Guowei Ma created FLINK-14466: - Summary: Let YarnJobClusterEntrypoint use user code class loader Key: FLINK-14466 URL: https://issues.apache.org/jira/browse/FLINK-14466 Project: Flink Issue

[jira] [Created] (FLINK-14465) Let StandaloneJobClusterEntrypoint use user code class loader

Guowei Ma created FLINK-14465: - Summary: Let StandaloneJobClusterEntrypoint use user code class loader Key: FLINK-14465 URL: https://issues.apache.org/jira/browse/FLINK-14465 Project: Flink

Re: [DISCUSS] FLIP-67: Global partitions lifecycle

Thanks Chesnay for proposing this FLIP! And sorry for the late response on it. The FLIP overall looks good to me, except for one question. - If a cluster partition does not exist in RM, how can users tell whether it is not produced yet, or it is already released? Users/InteractiveQuery may need