A couple of minor issues with empty names: It will not be possible to configure such operators from an XML file other than through wildcards.
Also, the AM log messages will not be as informative with an empty name, e.g. 2016-08-02 10:04:24,294 INFO com.datatorrent.stram.ResourceRequestHandler: Strict anti-affinity = [] for container with operators PTOperator[id=3,name=JdbcOutput] Ram On Thu, Aug 4, 2016 at 10:03 AM, Sanjay Pujare <[email protected]> wrote: > I differ. For the UI to render a DAG the names are useful, but if the name > is not required by the engine i.e. the engine is able to execute your > application fine with empty or null strings as names, is there any reason > to make them mandatory? > > On the other hand, we can come up with a scheme for system generated names > when the caller doesn’t provide a name. I have some ideas. > > > On 8/4/16, 9:48 AM, "Munagala Ramanath" <[email protected]> wrote: > > I don't see any reason to allow either. > > Ram > > On Thu, Aug 4, 2016 at 8:51 AM, Vlad Rozov <[email protected]> > wrote: > > > Currently addOperator/addStream/addModule allows both null and empty > > string in the operator/stream/module names. Is there any reason to > allow > > empty string? Should empty string and null be disallowed in those > APIs? > > > > Vlad > > > > > >
