----Original Mail ------
Sender:Piotr Nowojski
Send Date:Mon Jan 18 18:23:36 2021
Recipients:dev
Subject:Re: [DISCUSS] Dealing with deprecated and legacy code in
Flink
Hi Timo,
Thanks for starting this discussion. I'm not sure how we should
approach
this topic and what shou
t;
> >> > wrote:
> >> >
> >> > > Hi,
> >> > >
> >> > > Very thanks for @Timo to initiate the discussion!
> >> > >
> >> > > I would also +1 for providing some informations to users via
> >> annot
> >
>> > > I would also +1 for providing some informations to users via
>> annotations
>> > > or documents in advanced to not suprise users before we actually
>> remove
>> > > the legacy code.
>> > > If we finally decide to change one functionality that
> > If we finally decide to change one functionality that user could
> sense,
> > > > perhaps one
> > > > premise is that Flink has provided a replacement for that one and
> users
> > > > could transfer their
> > > > applications easily. Then we m
do the
> > transfer.
> > >
> > > To make the decision of whether to remove some legacy code, we might
> also
> > > consider to have a survey
> > > like the one we did for mesos support [1] to see how this functionality
> > is
> > > used.
> >
gt; [1]
> >
> https://lists.apache.org/thread.html/r139b11190a6d1f09c9e44d5fa985fd8d310347e66d2324ec1f0c2d87%40%3Cuser.flink.apache.org%3E
> >
> >
> >
> > --Original Mail --
> > Sender:Piotr Nowojski
> > Send Date:Mon Ja
inal Mail --
> Sender:Piotr Nowojski
> Send Date:Mon Jan 18 18:23:36 2021
> Recipients:dev
> Subject:Re: [DISCUSS] Dealing with deprecated and legacy code in Flink
> Hi Timo,
>
> Thanks for starting this discussion. I'm not sure how we should approach
> this topic
--Original Mail --
Sender:Piotr Nowojski
Send Date:Mon Jan 18 18:23:36 2021
Recipients:dev
Subject:Re: [DISCUSS] Dealing with deprecated and legacy code in Flink
Hi Timo,
Thanks for starting this discussion. I'm not sure how we should approach
this topic and
Hi Timo,
Thanks for starting this discussion. I'm not sure how we should approach
this topic and what should be our final recommendation, but definitely
clearing up a couple of things would be helpful.
For starters, I agree it would be good to have some more information,
besides just "@Deprecated
Hi everyone,
I would like to start a discussion how we treat deprecated and legacy
code in Flink in the future. During the last years, our code base has
grown quite a bit and a couple of interfaces and components have been
reworked on the way.
I'm sure each component has a few legacy parts t
10 matches
Mail list logo
