[jira] [Created] (FLINK-26617) Pass Kafka headers to remote functions and egresses

[Fil Karnicki (Jira)]

Fil Karnicki created FLINK-26617:


 Summary: Pass Kafka headers to remote functions and egresses
 Key: FLINK-26617
 URL: https://issues.apache.org/jira/browse/FLINK-26617
 Project: Flink
  Issue Type: Improvement
  Components: Stateful Functions
Reporter: Fil Karnicki


Typically OpenTelemetry (FLINK-22390) tracing spans get passed in kafka 
headers. We could be passing not only the Kafka ConsumerRecord value, but also 
the headers to remote functions, if the user configures their kafka ingress to 
do so

Similarly, kafka egresses could be configurable so that headers get passed on 
via the KafkaProducerRecord proto to kafka



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New Apache Flink Committer - Martijn Visser

[Guowei Ma]

Congrats Martijn!
Best,
Guowei


On Fri, Mar 11, 2022 at 10:36 PM Marios Trivyzas  wrote:

> Congrats Martijn!!
>
> Best,
> Marios
>
> On Thu, Mar 10, 2022 at 4:50 PM yu'an huang  wrote:
>
> > Congrats, Martijn!
> >
> >
> > Best
> > Yuan
> >
> >
> > > On 3 Mar 2022, at 11:49 PM, Robert Metzger 
> wrote:
> > >
> > > Hi everyone,
> > >
> > > On behalf of the PMC, I'm very happy to announce Martijn Visser as a
> new
> > > Flink committer.
> > >
> > > Martijn is a very active Flink community member, driving a lot of
> efforts
> > > on the dev@flink mailing list. He also pushes projects such as
> replacing
> > > Google Analytics with Matomo, so that we can generate our web analytics
> > > within the Apache Software Foundation.
> > >
> > > Please join me in congratulating Martijn for becoming a Flink
> committer!
> > >
> > > Cheers,
> > > Robert
> >
> >
>
> --
> Marios
>

[jira] [Created] (FLINK-26618) Remove jar statement not aligned with pipleline.jars

[Paul Lin (Jira)]

Paul Lin created FLINK-26618:


 Summary: Remove jar statement not aligned with pipleline.jars
 Key: FLINK-26618
 URL: https://issues.apache.org/jira/browse/FLINK-26618
 Project: Flink
  Issue Type: Bug
Affects Versions: 1.14.3
Reporter: Paul Lin


Currently, `remove jar` statement doesn't remove the corresponding jars in 
pipeline options.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (FLINK-26619) Write the window allocator usage document of pyflink data flow API

[zhangjingcun (Jira)]

zhangjingcun created FLINK-26619:


 Summary: Write the window allocator usage document of pyflink data 
flow API
 Key: FLINK-26619
 URL: https://issues.apache.org/jira/browse/FLINK-26619
 Project: Flink
  Issue Type: New Feature
  Components: API / Python
Affects Versions: 1.14.4
Reporter: zhangjingcun


Write the window allocator usage document of pyflink data flow API



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [DISCUSS] Preview release for Flink Kubernetes Operator

[Yang Wang]

Thanks Gyula for starting this discussion.

Given that the core functionality is closing to stable, I am in favor of
having the MVP release at the end of March.
The first release will help us to collect more feedbacks from the users.
Also it is a good chance to let the users know that the community is trying
to maintain an official Kubernetes operator :)
I hope that the companies could build their own production streaming
platform on top of the flink-kubernetes-operator in the future.

FYI: @Wenjun Min is still working hard on supporting the Session Job in
Flink Kubernetes operator, It will be great if we could include it in the
first release.
And I believe we have enough time.

Moreover, I agree with you that we need to invest more time in the
documentation, e2e tests, helm install optimization, logging,
etc. before the release.


Best,
Yang


Gyula Fóra  于2022年3月12日周六 01:10写道：

> Hi Team!
>
> I would like to discuss the timeline for the initial preview/milestone
> release of the flink-kubernetes-operator
>  project.
>
> The last few weeks we have been working very hard with the community to
> stabilize the initial feature set and I think we have made great progress.
> While we are still far from a production ready-state, a preview release
> will give us the opportunity to reach more people and gather much needed
> input to take this project to the next level.
>
> There are still a couple missing features that we need to iron out and we
> need to make sure we have proper documentation but after that I think it
> would be a good time for the preview release.
>
> I propose to aim for the first release candidate around the 25-27th of
> March after which we should dedicate a few days for some extensive testing
> and bugfixing.
>
> What do you think?
>
> Gyula
>