Re: [DISCUSS] KIP-706: Add method "Producer#produce" to return CompletionStage instead of Future

[Govinda Sakhare]

Hi,

Indeed `transmit(msg)` looks good. Another option could be `publish(msg)`

Best Regards,
Govinda


On Sat, Jan 30, 2021, 17:45 Chia-Ping Tsai  wrote:

> hi Jason
>
> Thanks for your response. "transmit" is good to me.
>
> As we discussed by email, KIP-706 is going to be merged to KIP-691(
> https://cwiki.apache.org/confluence/x/PSfZCQ). Hence, please feel free to
> replace "produce" by "transmit" in KIP-691.
>
> Best,
> Chia-Ping
>
> On 2021/01/30 00:48:38, Jason Gustafson  wrote:
> > Hi Chia-Ping,
> >
> > I think this is a great idea. It is a pity that we cannot continue to use
> > the `send` verb, but I don't see how we can. I know we considered
> > `transmit` as another option which is closer to `send`. That would avoid
> > the redundancy when people choose the common "producer" variable name.
> >
> > producer.transmit
> >
> > instead of
> >
> > producer.produce
> >
> > A couple alternatives might be `write` or `append`. I'm happy with
> > `produce` as well, but curious if others have thoughts.
> >
> > -Jason
> >
> >
> > On Wed, Jan 20, 2021 at 9:37 AM Chia-Ping Tsai 
> wrote:
> >
> > > Dear all,
> > >
> > > I'd like to start the discussion thread for KIP-706:
> > >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829459
> > >
> > > KIP-706 is proposing to introduce new API "CompletionStage
> > > produce(record)" to Producer. Kafka users can leverage CompletionStage
> to
> > > write asynchronous non-blocking code. CompletionStage is more powerful
> than
> > > Future and callback. Also, the code using Future and callback can be
> easily
> > > re-written by CompletionStage.
> > >
> > > Cheers,
> > > Chia-Ping
> > >
> > >
> >
>

Re: Why many "Load Bug xxx" JIRA bug by Tim?

[Govinda Sakhare]

Hi,

If it is possible, we should configure/enable Captcha to prevent automated
spamming attacks.

Thanks
Govinda

On Wed, Jan 6, 2021 at 11:30 PM Matthias J. Sax  wrote:

> This was a spamming attack.
>
> The user was blocked and the corresponding tickets were deleted. (Cf.
> https://issues.apache.org/jira/browse/INFRA-21268)
>
> The "problem" is, that anybody can create an Jira account and create
> tickets. It's in the spirit of open source and the ASF to not lock down
> Jira, to make it easy for people to report issues.
>
> The drawback is, that stuff like this can happen. It's easy to write a
> bot to spam the Jira board...
>
> Because Jira is managed by the ASF infra-team, Kafka committers/PMC
> cannot block users and thus it takes a little longer to react to an
> issue like this, as we need to wait for the infra team to help out.
>
>
> -Matthias
>
>
> On 1/6/21 1:14 AM, M. Manna wrote:
> > I had to register this as spam and block them. I couldn’t disable it from
> > ASF JiRA.
> >
> >  I’m also curious to know how/why such surge occurred.
> >
> > Regards,
> >
> > On Wed, 6 Jan 2021 at 03:45, Luke Chen  wrote:
> >
> >> Hi,
> >> I received a lot of JIRA notification emails today, and they are all
> >> titled: "Load Bug xxx" by Tim.
> >> The bug content doesn't look like a real bug, they are like generated by
> >> automation.
> >> I'm wondering why that could happen?
> >> Do we have any way to delete them all?
> >>
> >> Thanks.
> >> Luke
> >>
> >
>


-- 
Thanks  & Regards,
Govinda Sakhare.