-1 for splitting user list to areas in Flink.
As Robert and others have chimed in, we could have separate user list for
sub projects in Flink, like statefun
- Henry
On Tue, Mar 2, 2021, 11:27 AM Roman Khachatryan wrote:
> Thanks Robert,
>
> That's a good idea, let's revisit it later.
>
> Regar
Thanks Robert,
That's a good idea, let's revisit it later.
Regards,
Roman
On Tue, Mar 2, 2021 at 3:40 PM Robert Metzger wrote:
> Thanks a lot for bringing up this idea Roman!
>
> After reading the initial proposal, I quite liked the idea, because it
> makes our life easier: We can only monito
Thanks a lot for bringing up this idea Roman!
After reading the initial proposal, I quite liked the idea, because it
makes our life easier: We can only monitor lists relevant for the topics we
are working on (I have to admit that I usually skip all questions that seem
to be related to SQL or State
@tzuli...@apache.org
> instead of splitting into “sub-lists”, we should simply have dedicated
“sub-topic maintainers” assigned.
I think this could also work, but some mails may fall between the filters.
@i...@ververica.com
I guess the previous decision about StateFun ML was made in a bit differe
Hi Roman,
Regarding StateFun having a separate mailing list, I'm ok with it going
either-way, however when we first contributed
the project there was already a discussion about having a separate mailing
list for StateFun [1] and the feedback was
having StateFun be part of the regular mailing list.
Hi,
I feel that the issues Roman has pointed out so far, is less a problem of
all topics (SQL / PyFlink / StateFun) being on the same list, and more a
problem that we are missing dedicated groups of “user support shepherds”
who are specifically responsible for individual topics on a day-to-day
bas
Thanks for your replies!
@Konstantin Knauf
> Why do you think the quality and speed of answers would improve with
dedicated lists?
If there is a question on something that you are not an expert in; then you
either have to
- pull in someone who is more experienced in it (more time on hops, esp. if
As others I'd also rather be -1 on splitting (even splitting out the
statefun).
Personally I don't find it problematic. I often find the subjects quite
descriptive, they often include tags or mention which API they refer to.
If they don't I am quite sure having separate sub-lists would not help
in
I would vote -0 here.
I fear that we are creating potential silos where a team doesn't know
what is going on in the other teams.
Regards,
Timo
On 01.03.21 10:47, Jark Wu wrote:
I also have some concerns about splitting python and sql.
Because I have seen some SQL questions users reported bu
I also have some concerns about splitting python and sql.
Because I have seen some SQL questions users reported but is related to
deployment or state backend.
Best,
Jark
On Mon, 1 Mar 2021 at 17:15, Konstantin Knauf
wrote:
> Hi Roman,
>
> I slightly +1 for a list dedicated to Statefun users, bu
Hi Roman,
I slightly +1 for a list dedicated to Statefun users, but -1 for splitting
up the rest. I think there are still a lot of crosscutting concerns between
Python, DataStream, Table API and SQL where users of another API can also
help out, too. It also requires users to think about which list
Hi Roman,
This is a very good idea. I will look forward to the official setting up
"sub-lists" as soon as possible and sharing development experience and problems
with friends in a certain field.
Regards,
yue
xiao...@ysstech.com
From: Roman Khachatryan
Date: 2021-03-01 16:48
To: dev
Subjec
12 matches
Mail list logo
