Hello there,
New to the community. Just thought you might want some inputs from new
comers too.
I prefer option 2, where you need to prove the ability and commitment with
commits before contributor permission is assigned.
Cheers,
Feng
Le lun. 15 avr. 2019 à 09:17, Robert Metzger a écrit :
>
; Regarding your particular contribution, I think it's worth to include it
> > in 1.8 release, therefore I marked it as a Blocker, will try to review
> > it next few days or find a person to do that.
> >
> > Best,
> >
> > Dawid
> >
> >
Hello guys,
Sorry if this is already discussed question, is there some guidance in
place to help new Flink developers to integrate to the community ?
I’m new to the community and super happy after submitting my first pull
request ( https://github.com/apache/flink/pull/7726 ) after some
discussion
Hello guys,
Just wondering if someone can help me out with this very first pull request
- the travis-ci failed during Tests phase :
https://travis-ci.org/apache/flink/builds/494787984
The error seems unrelevant to my change though, do I need some trick to fix
it here?
10:42:12.053 [ERROR] Failed
would be worth to still add that
> as a safeguard, just in case.
>
> What do you think?
>
> Cheers,
> Gordon
>
> On Fri, Feb 15, 2019, 11:06 PM Feng LI wrote:
>
> > Hello Gordon,
> >
> > Thanks for adding the contributor permission. :)
> >
> &
ll slightly in favor of keeping the default behaviour for the
> > current Kafka connector,
> > and only change that default for the upcoming rework of the connector.
> >
> > Cheers,
> > Gordon
> >
> > On Fri, Feb 15, 2019 at 10:13 PM Feng LI wrote:
> >
>
ould almost consider this to be a bug , can’t see any reasonable use
> > case just hard to debug problems .
> >
> > Having an option would be a good start but I would rather treat this as a
> > bug.
> >
> > Gyula
> >
> > On Wed, 13 Feb 2019 at 18:27,
Hello there,
I’m just wondering if there are real world use cases for maintaining this
default behavior. It’s a bit counter intuitive and sometimes results in
serious production issues. ( We had a similar issue when changing the topic
name, and resulting reading every message twice - both from the
