+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.
