Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
In-Reply-To: <7C1A5DB1-F942-462B-AD63-BE097F74539D@datatorrent.com>
References: <fb53bf2e-153c-6a37-f956-3c4fa5766213@datatorrent.com>
 <CAJ484BgX0VS9q66y=8efPs_yvBoDCkwL+f4iUqtvj8-Mv2xQ_w@mail.gmail.com> <7C1A5DB1-F942-462B-AD63-BE097F74539D@datatorrent.com>
From: Munagala Ramanath <ram@datatorrent.com>
Date: Thu, 4 Aug 2016 10:36:04 -0700
Message-ID: <CAJ484BjDNjDsJa43xp-jG7vkbpQpPsg-VRBSt2oy=2APeUMwjw@mail.gmail.com>
Subject: Re: empty operator/stream/module names
To: dev@apex.apache.org
Content-Type: multipart/alternative; boundary=94eb2c11915e60975a05394262d8
archived-at: Thu, 04 Aug 2016 17:36:17 -0000

--94eb2c11915e60975a05394262d8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It will not be possible to configure such operators from an XML file other
than through
wildcards -- but maybe that's OK.

Ram

On Thu, Aug 4, 2016 at 10:03 AM, Sanjay Pujare <sanjay@datatorrent.com>
wrote:

> I differ. For the UI to render a DAG the names are useful, but if the nam=
e
> 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 name=
s
> when the caller doesn=E2=80=99t provide a name. I have some ideas.
>
>
> On 8/4/16, 9:48 AM, "Munagala Ramanath" <ram@datatorrent.com> wrote:
>
>     I don't see any reason to allow either.
>
>     Ram
>
>     On Thu, Aug 4, 2016 at 8:51 AM, Vlad Rozov <v.rozov@datatorrent.com>
> wrote:
>
>     > Currently addOperator/addStream/addModule allows both null and empt=
y
>     > 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
>     >
>
>
>
>

--94eb2c11915e60975a05394262d8--