You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by David Yan <da...@datatorrent.com> on 2016/03/07 22:52:24 UTC
Naming: STRAM and StreamingContainer
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
Re: Naming: STRAM and StreamingContainer
Posted by Isha Arkatkar <is...@datatorrent.com>.
+1 for Apex App Master, and Apex Worker
We have a few other classes with StreamingContainer prefix e.g.
StreamingContainerManager, StreamingContainerAgent. Should we consider
renaming these as well?
Thanks,
Isha
On Mon, Mar 7, 2016 at 4:12 PM, Chandni Singh <ch...@datatorrent.com>
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 <
> ashwinchandrap@gmail.com> 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 <ch...@datatorrent.com>
> > 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 <
> > > ashwinchandrap@gmail.com> 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 <da...@datatorrent.com>
> > wrote:
> > > >
> > > > > +1 for "Apex Worker".
> > > > >
> > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > chandni@datatorrent.com
> > > >
> > > > > 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 <
> > thomas@datatorrent.com
> > > >
> > > > > > 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 <
> david@datatorrent.com
> > >
> > > > > 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.
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Chinmay Kolhatkar <ch...@datatorrent.com>.
+1 for Apex Master and apex worker.
On 8 Mar 2016 10:53 a.m., "Satish Gopalani" <go...@gmail.com> wrote:
> +1 for Apex Master and Apex Worker
>
> Thanks,
> Satish Gopalani
>
> On Tue, Mar 8, 2016 at 10:46 AM, Milind Barve <mi...@gmail.com> wrote:
>
> > +1 for Apex Master and Apex worker.
> > On Mar 8, 2016 10:27 AM, "Sandeep Deshmukh" <sa...@datatorrent.com>
> > wrote:
> >
> > > +1 for Apex App Master, and Apex Worker.
> > >
> > > Regards,
> > > Sandeep
> > >
> > > On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta <
> > > ashwinchandrap@gmail.com> 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 <
> chandni@datatorrent.com
> > >
> > > > 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 <
> > > > > ashwinchandrap@gmail.com> 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 <
> > > chandni@datatorrent.com
> > > > >
> > > > > > 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 <
> > > > > > > ashwinchandrap@gmail.com> 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 <
> > david@datatorrent.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 for "Apex Worker".
> > > > > > > > >
> > > > > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > > > > > chandni@datatorrent.com
> > > > > > > >
> > > > > > > > > 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 <
> > > > > > thomas@datatorrent.com
> > > > > > > >
> > > > > > > > > > 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 <
> > > > > david@datatorrent.com
> > > > > > >
> > > > > > > > > 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.
>
Re: Naming: STRAM and StreamingContainer
Posted by Pradeep Kumbhar <pr...@datatorrent.com>.
+1 ApexAppMaster and ApexWorker
On Tue, Mar 8, 2016 at 10:53 AM, Satish Gopalani <go...@gmail.com>
wrote:
> +1 for Apex Master and Apex Worker
>
> Thanks,
> Satish Gopalani
>
> On Tue, Mar 8, 2016 at 10:46 AM, Milind Barve <mi...@gmail.com> wrote:
>
> > +1 for Apex Master and Apex worker.
> > On Mar 8, 2016 10:27 AM, "Sandeep Deshmukh" <sa...@datatorrent.com>
> > wrote:
> >
> > > +1 for Apex App Master, and Apex Worker.
> > >
> > > Regards,
> > > Sandeep
> > >
> > > On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta <
> > > ashwinchandrap@gmail.com> 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 <
> chandni@datatorrent.com
> > >
> > > > 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 <
> > > > > ashwinchandrap@gmail.com> 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 <
> > > chandni@datatorrent.com
> > > > >
> > > > > > 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 <
> > > > > > > ashwinchandrap@gmail.com> 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 <
> > david@datatorrent.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 for "Apex Worker".
> > > > > > > > >
> > > > > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > > > > > chandni@datatorrent.com
> > > > > > > >
> > > > > > > > > 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 <
> > > > > > thomas@datatorrent.com
> > > > > > > >
> > > > > > > > > > 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 <
> > > > > david@datatorrent.com
> > > > > > >
> > > > > > > > > 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.
>
--
*regards,*
*~pradeep*
Re: Naming: STRAM and StreamingContainer
Posted by Satish Gopalani <go...@gmail.com>.
+1 for Apex Master and Apex Worker
Thanks,
Satish Gopalani
On Tue, Mar 8, 2016 at 10:46 AM, Milind Barve <mi...@gmail.com> wrote:
> +1 for Apex Master and Apex worker.
> On Mar 8, 2016 10:27 AM, "Sandeep Deshmukh" <sa...@datatorrent.com>
> wrote:
>
> > +1 for Apex App Master, and Apex Worker.
> >
> > Regards,
> > Sandeep
> >
> > On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta <
> > ashwinchandrap@gmail.com> 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 <chandni@datatorrent.com
> >
> > > 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 <
> > > > ashwinchandrap@gmail.com> 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 <
> > chandni@datatorrent.com
> > > >
> > > > > 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 <
> > > > > > ashwinchandrap@gmail.com> 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 <
> david@datatorrent.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > +1 for "Apex Worker".
> > > > > > > >
> > > > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > > > > chandni@datatorrent.com
> > > > > > >
> > > > > > > > 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 <
> > > > > thomas@datatorrent.com
> > > > > > >
> > > > > > > > > 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 <
> > > > david@datatorrent.com
> > > > > >
> > > > > > > > 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.
Re: Naming: STRAM and StreamingContainer
Posted by Milind Barve <mi...@gmail.com>.
+1 for Apex Master and Apex worker.
On Mar 8, 2016 10:27 AM, "Sandeep Deshmukh" <sa...@datatorrent.com> wrote:
> +1 for Apex App Master, and Apex Worker.
>
> Regards,
> Sandeep
>
> On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta <
> ashwinchandrap@gmail.com> 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 <ch...@datatorrent.com>
> > 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 <
> > > ashwinchandrap@gmail.com> 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 <
> chandni@datatorrent.com
> > >
> > > > 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 <
> > > > > ashwinchandrap@gmail.com> 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 <david@datatorrent.com
> >
> > > > wrote:
> > > > > >
> > > > > > > +1 for "Apex Worker".
> > > > > > >
> > > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > > > chandni@datatorrent.com
> > > > > >
> > > > > > > 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 <
> > > > thomas@datatorrent.com
> > > > > >
> > > > > > > > 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 <
> > > david@datatorrent.com
> > > > >
> > > > > > > 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.
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Sandeep Deshmukh <sa...@datatorrent.com>.
+1 for Apex App Master, and Apex Worker.
Regards,
Sandeep
On Tue, Mar 8, 2016 at 7:07 AM, Ashwin Chandra Putta <
ashwinchandrap@gmail.com> 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 <ch...@datatorrent.com>
> 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 <
> > ashwinchandrap@gmail.com> 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 <chandni@datatorrent.com
> >
> > > 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 <
> > > > ashwinchandrap@gmail.com> 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 <da...@datatorrent.com>
> > > wrote:
> > > > >
> > > > > > +1 for "Apex Worker".
> > > > > >
> > > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > > chandni@datatorrent.com
> > > > >
> > > > > > 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 <
> > > thomas@datatorrent.com
> > > > >
> > > > > > > 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 <
> > david@datatorrent.com
> > > >
> > > > > > 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.
>
Re: Naming: STRAM and StreamingContainer
Posted by Ashwin Chandra Putta <as...@gmail.com>.
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 <ch...@datatorrent.com>
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 <
> ashwinchandrap@gmail.com> 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 <ch...@datatorrent.com>
> > 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 <
> > > ashwinchandrap@gmail.com> 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 <da...@datatorrent.com>
> > wrote:
> > > >
> > > > > +1 for "Apex Worker".
> > > > >
> > > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> > chandni@datatorrent.com
> > > >
> > > > > 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 <
> > thomas@datatorrent.com
> > > >
> > > > > > 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 <
> david@datatorrent.com
> > >
> > > > > 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.
Re: Naming: STRAM and StreamingContainer
Posted by Chandni Singh <ch...@datatorrent.com>.
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 <
ashwinchandrap@gmail.com> 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 <ch...@datatorrent.com>
> 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 <
> > ashwinchandrap@gmail.com> 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 <da...@datatorrent.com>
> wrote:
> > >
> > > > +1 for "Apex Worker".
> > > >
> > > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <
> chandni@datatorrent.com
> > >
> > > > 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 <
> thomas@datatorrent.com
> > >
> > > > > 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 <david@datatorrent.com
> >
> > > > 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.
>
Re: Naming: STRAM and StreamingContainer
Posted by Ashwin Chandra Putta <as...@gmail.com>.
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 <ch...@datatorrent.com>
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 <
> ashwinchandrap@gmail.com> 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 <da...@datatorrent.com> wrote:
> >
> > > +1 for "Apex Worker".
> > >
> > > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <chandni@datatorrent.com
> >
> > > 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 <thomas@datatorrent.com
> >
> > > > 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 <da...@datatorrent.com>
> > > 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.
Re: Naming: STRAM and StreamingContainer
Posted by Chandni Singh <ch...@datatorrent.com>.
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 <
ashwinchandrap@gmail.com> 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 <da...@datatorrent.com> wrote:
>
> > +1 for "Apex Worker".
> >
> > On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <ch...@datatorrent.com>
> > 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 <th...@datatorrent.com>
> > > 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 <da...@datatorrent.com>
> > 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.
>
Re: Naming: STRAM and StreamingContainer
Posted by Ashwin Chandra Putta <as...@gmail.com>.
+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 <da...@datatorrent.com> wrote:
> +1 for "Apex Worker".
>
> On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <ch...@datatorrent.com>
> 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 <th...@datatorrent.com>
> > 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 <da...@datatorrent.com>
> 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.
Re: Naming: STRAM and StreamingContainer
Posted by David Yan <da...@datatorrent.com>.
+1 for "Apex Worker".
On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <ch...@datatorrent.com>
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 <th...@datatorrent.com>
> 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 <da...@datatorrent.com> 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
> > >
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Pramod Immaneni <pr...@datatorrent.com>.
Apex App Master and Apex Worker sounds good.
On Mon, Mar 7, 2016 at 2:17 PM, Chandni Singh <ch...@datatorrent.com>
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 <th...@datatorrent.com>
> 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 <da...@datatorrent.com> 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
> > >
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Chandni Singh <ch...@datatorrent.com>.
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 <th...@datatorrent.com> 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 <da...@datatorrent.com> 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
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by David Yan <da...@datatorrent.com>.
I think this name change will only happen when we have our next major
release. At that point, we won't have com.datatorrent anywhere in Apex
code. Everything will be changed to org.apache.apex.
David
On Tue, Mar 8, 2016 at 10:40 AM, Vlad Rozov <v....@datatorrent.com> wrote:
> Will the change affect "com.datatorrent.stram" package name and few dozen
> classes that start with "Stram"? If not, other than documentation what will
> be affected by the rename? Will the rename lead to any backward
> compatibility problems?
>
> Thank you,
>
> Vlad
>
>
> On 3/7/16 14:14, Thomas Weise 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 <da...@datatorrent.com> 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
>>>
>>>
>
Re: Naming: STRAM and StreamingContainer
Posted by Vlad Rozov <v....@datatorrent.com>.
Will the change affect "com.datatorrent.stram" package name and few
dozen classes that start with "Stram"? If not, other than documentation
what will be affected by the rename? Will the rename lead to any
backward compatibility problems?
Thank you,
Vlad
On 3/7/16 14:14, Thomas Weise 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 <da...@datatorrent.com> 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
>>
Re: Naming: STRAM and StreamingContainer
Posted by Thomas Weise <th...@datatorrent.com>.
Because we want to know and make it clear that the JVM processes with this
main class belong to Apex applications.
On Mon, Mar 7, 2016 at 2:31 PM, Sandesh Hegde <sa...@datatorrent.com>
wrote:
> Why do we even need to tag Apex? how about just worker and app master?
>
> On Mon, Mar 7, 2016 at 2:21 PM Thomas Weise <th...@datatorrent.com>
> 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 <da...@datatorrent.com> 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
> > >
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Sandesh Hegde <sa...@datatorrent.com>.
Why do we even need to tag Apex? how about just worker and app master?
On Mon, Mar 7, 2016 at 2:21 PM Thomas Weise <th...@datatorrent.com> 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 <da...@datatorrent.com> 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
> >
>
Re: Naming: STRAM and StreamingContainer
Posted by Thomas Weise <th...@datatorrent.com>.
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 <da...@datatorrent.com> 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
>