+1 for Apex Master and apex worker. On 8 Mar 2016 10:53 a.m., "Satish Gopalani" <[email protected]> wrote:
> +1 for Apex Master and Apex Worker > > Thanks, > Satish Gopalani > > On Tue, Mar 8, 2016 at 10:46 AM, Milind Barve <[email protected]> wrote: > > > +1 for Apex Master and Apex worker. > > On Mar 8, 2016 10:27 AM, "Sandeep Deshmukh" <[email protected]> > > wrote: > > > > > +1 for Apex App Master, and Apex Worker. > > > > > > Regards, > > > Sandeep > > > > > > On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta < > > > [email protected]> wrote: > > > > > > > Valid point about the Operator being abstraction for business logic, > it > > > is > > > > the Node object that executes the business logic in the Operator. > > > > > > > > However, just by having the main method in the class does not make > it a > > > > worker, the app master also has a main method. StreamingContainer is > a > > > > handler that spawns up a thread per Node object corresponding to each > > > > operator in the container, the node object in turn executes the work > in > > > the > > > > corresponding operator. > > > > > > > > So the StreamingContainer by itself is not a worker, I would rather > > call > > > it > > > > a Handler or a Manager. Or even call it a SubMaster within a > container > > > and > > > > then call Node object as Worker. > > > > > > > > Regards, > > > > Ashwin. > > > > > > > > On Mon, Mar 7, 2016 at 4:12 PM, Chandni Singh < > [email protected] > > > > > > > wrote: > > > > > > > > > Isn't operator the entity that performs the actual work/task? > > > > > > > > > > I don't think so. Operator is an abstraction for business logic. It > > is > > > > not > > > > > the class with the main method. The main class here is the > > > > > StreamingContainer which will executes the business logic provided > in > > > the > > > > > operator. > > > > > > > > > > Chandni > > > > > > > > > > On Mon, Mar 7, 2016 at 3:58 PM, Ashwin Chandra Putta < > > > > > [email protected]> wrote: > > > > > > > > > > > Isn't operator the entity that performs the actual work/task? > From > > > > what I > > > > > > know, the StreamingContainer is more of a handler of operators > > within > > > > the > > > > > > container. > > > > > > > > > > > > Regards, > > > > > > Ashwin. > > > > > > > > > > > > On Mon, Mar 7, 2016 at 3:26 PM, Chandni Singh < > > > [email protected] > > > > > > > > > > > wrote: > > > > > > > > > > > > > How about calling StreamingContainer as > > > > > > ApexWorkerHandler/ApexWorkerManager > > > > > > > as it is possible that there can be multiple operators within a > > > > > container > > > > > > > and each operator by itself is a worker. > > > > > > > > > > > > > > IMO an operator is not a worker. At least we haven't been > > calling > > > > it a > > > > > > > 'Worker' so far. > > > > > > > Apex worker corresponds to a child container and can run > multiple > > > > > > operators > > > > > > > if that is the case. > > > > > > > > > > > > > > Chandni > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 7, 2016 at 3:20 PM, Ashwin Chandra Putta < > > > > > > > [email protected]> wrote: > > > > > > > > > > > > > > > +1 for ApexAppMaster. > > > > > > > > > > > > > > > > How about calling StreamingContainer as > > > > > > > ApexWorkerHandler/ApexWorkerManager > > > > > > > > as it is possible that there can be multiple operators > within a > > > > > > container > > > > > > > > and each operator by itself is a worker. > > > > > > > > > > > > > > > > Regards, > > > > > > > > Ashwin. > > > > > > > > > > > > > > > > On Mon, Mar 7, 2016 at 2:51 PM, David Yan < > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > +1 for "Apex Worker". > > > > > > > > > > > > > > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh < > > > > > > [email protected] > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > How about renaming them to Apex App Master, and Apex > Worker > > > > > > > Container? > > > > > > > > > > I think just Apex Worker is sufficient if we make this > > > change. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 7, 2016 at 2:14 PM, Thomas Weise < > > > > > > [email protected] > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > I like the suggestion. Can we record it in JIRA for the > > > next > > > > > > major > > > > > > > > > > release? > > > > > > > > > > > > > > > > > > > > > > On Mon, Mar 7, 2016 at 1:52 PM, David Yan < > > > > > [email protected] > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > Today, in both our doc and our code, we use the name > > > STRAM > > > > > > > > (STReaming > > > > > > > > > > App > > > > > > > > > > > > Master) for the App Master, and StreamingContainer > > > > > (previously > > > > > > > > known > > > > > > > > > as > > > > > > > > > > > > StramChild) for the worker containers. > > > > > > > > > > > > > > > > > > > > > > > > But since STRAM is running in a container itself, > > calling > > > > the > > > > > > > > worker > > > > > > > > > > > > containers StreamingContainer is not exactly ideal. > > > > > > > > > > > > > > > > > > > > > > > > How about renaming them to Apex App Master, and Apex > > > Worker > > > > > > > > > Container? > > > > > > > > > > > > Thoughts? > > > > > > > > > > > > > > > > > > > > > > > > David > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > Regards, > > > > > > > > Ashwin. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Regards, > > > > > > Ashwin. > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Regards, > > > > Ashwin. > > > > > > > > > > > > > -- > > Thanks and regards, > Satish M Gopalani. >
