apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Smith, Kent" <Kent.Smi...@capitalone.com>
Subject RE: Input Operator Question
Date Mon, 25 Jan 2016 22:33:13 GMT
Wait, additional newbee question.  So an Operator runs in own thread.  Do you mean a given
Operator is shared or could multiple threads, external to the Operator thread call the same
operator and each get an operator thread of their own (within their context) or would each
thread call within the Operator thread one at a time so each context shares the Operator thread?

Thanks.

-----Original Message-----
From: Bryan Bende [mailto:bbende@gmail.com] 
Sent: Monday, January 25, 2016 5:27 PM
To: dev@apex.incubator.apache.org
Subject: Re: Input Operator Question

Thanks! Appreciate the quick response.

On Mon, Jan 25, 2016 at 5:22 PM, Ashwin Chandra Putta < ashwinchandrap@gmail.com> wrote:

> It always called sequentially in a single thread. A given operator 
> runs in its main thread and all the calls on the operator are called 
> with in the same thread.
>
> Regards,
> Ashwin.
>
> On Mon, Jan 25, 2016 at 2:13 PM, Bryan Bende <bbende@gmail.com> wrote:
>
> > Hello,
> >
> > Quick beginner question regarding the life-cycle of operators...
> >
> > Can emitTuples() get called concurrently by multiple threads? or is 
> > it always called sequentially for a given window until endWindow() 
> > is
> called?
> >
> > Thanks,
> >
> > Bryan
> >
>
>
>
> --
>
> Regards,
> Ashwin.
>
________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to Capital One
and/or its affiliates and may only be used solely in performance of work or services for Capital
One. The information transmitted herewith is intended only for use by the individual or entity
to which it is addressed. If the reader of this message is not the intended recipient, you
are hereby notified that any review, retransmission, dissemination, distribution, copying
or other use of, or taking of any action in reliance upon this information is strictly prohibited.
If you have received this communication in error, please contact the sender and delete the
material from your computer.
Mime
View raw message