Mailing-List: contact users-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: <597F5EBD.5070404@windofkeltia.com>
References: <597F5EBD.5070404@windofkeltia.com>
From: Matt Gilman <matt.c.gilman@gmail.com>
Date: Tue, 1 Aug 2017 11:39:39 -0400
Message-ID: <CAFddr26c4asFZ273=tkStgjoeMD0qpeasnZ=YK+yyZQhLo6WkA@mail.gmail.com>
Subject: Re: New "hierarchical" controller service system confusing
To: users@nifi.apache.org
Content-Type: multipart/alternative; boundary="001a1141071ea174cf0555b2f482"
archived-at: Tue, 01 Aug 2017 15:39:46 -0000

--001a1141071ea174cf0555b2f482
Content-Type: text/plain; charset="UTF-8"

Russell,

Thanks for the suggestion on the improved Controller Service UX. Would you
mind filing a JIRA for this improvement?

In 1.x, the user can see the components referencing a Controller Service in
1 of 3 places. The references are shown in the read-only details dialog,
the service configuration dialog, and the enable/disable service dialog.
The references will include Processors, Reporting Tasks, and Controller
Services (and components that reference those services and so on).

Thanks

Matt


On Mon, Jul 31, 2017 at 12:45 PM, Russell Bateman <russ@windofkeltia.com>
wrote:

> Friends,
>
> I find the new (well, since 0.7.x -> 1.x) way of associating controller
> services based on the process group a bit disorienting. When one follows
> the right arrow from a consuming processor and lands on the Process Group
> Configuration page where the services are configured, one is obliged to
> click on the General tab to figure out whether the controller service is
> at the root (the case for services whose flows were upgraded from the 0.7.x
> world) or for a specific process group (the case for configuration
> accomplished post-upgrade/native 1.x).
>
> I realize that this will be a dwindling problem, but there's enough white
> space in this dialog to justify putting the Process Group Name to the right
> of the dialog title (Process Group Configuration) while on the Controller
> Services tab, even without the momentary confusion of origin (that is, a
> flow from 0.7.x vs. a "native" 1.x flow). So, I consider that this
> enhancement holds regardless of whether upgraded flows are present or not.
>
> At the same time, I'm tempted to ask how, when looking on the Controller
> Services tab/page, one figures out which processor instance(s) is (are)
> consuming a particular controller service I'm looking at?
>
> Russ
>

--001a1141071ea174cf0555b2f482
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Russell,<div><br></div><div>Thanks for the suggestion on t=
he improved Controller Service UX. Would you mind filing a JIRA for this im=
provement?</div><div><br></div><div>In 1.x,=C2=A0the user can see the compo=
nents referencing a Controller Service in 1 of 3 places. The references are=
 shown in the read-only details dialog, the service configuration dialog, a=
nd the enable/disable service dialog. The references will include Processor=
s, Reporting Tasks, and Controller Services (and components that reference =
those services and so on).</div><div><br></div><div>Thanks</div><div><br></=
div><div>Matt</div><div><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Mon, Jul 31, 2017 at 12:45 PM, Russell Bateman <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:russ@windofkeltia.com" target=3D"_bla=
nk">russ@windofkeltia.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
 =20

   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font face=3D"Candara">Friends,<br>
      <br>
      I find the new (well, since 0.7.x -&gt; 1.x) way of associating
      controller services based on the process group a bit disorienting.
      When one follows the right arrow from a consuming processor and
      lands on the </font><tt>Process Group Configuration</tt><font face=3D=
"Candara"> page where the services are configured, one is
      obliged to click on the </font><tt>General</tt><font face=3D"Candara"=
> tab to figure out whether the controller service
      is at the root (the case for services whose flows were upgraded
      from the 0.7.x world) or for a specific process group (the case
      for configuration accomplished post-upgrade/native 1.x).<br>
      <br>
      I realize that this will be a dwindling problem, but there&#39;s
      enough white space in this dialog to justify putting the Process
      Group Name to the right of the dialog title (</font><tt>Process
      Group Configuration</tt><font face=3D"Candara">) while on the </font>=
<tt>Controller
      Services</tt><font face=3D"Candara"> tab, even without the momentary
      confusion of origin (that is, a flow from 0.7.x vs. a &quot;native&qu=
ot; 1.x
      flow). So, I consider that this enhancement holds regardless of
      whether upgraded flows are present or not.<br>
      <br>
      At the same time, I&#39;m tempted to ask how, when looking on the
      Controller Services tab/page, one figures out which processor
      instance(s) is (are) consuming a particular controller service I&#39;=
m
      looking at?<br>
      <br>
      Russ<br>
    </font>
  </div>

</blockquote></div><br></div>

--001a1141071ea174cf0555b2f482--