You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Paresh Shah <Pa...@lifelock.com> on 2016/01/21 18:48:05 UTC
Unable to pick different input ports in the RemoteProcessorGroup
I have created different set of InputPorts for the different pipelines. But when I see the list of InputPorts in the RPG I do not see option to pick other ports except the first one in the list.
I have attached the screeshots
________________________________
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
Re: Unable to pick different input ports in the RemoteProcessorGroup
Posted by Joe Witt <jo...@gmail.com>.
ok great -thanks
On Thu, Jan 21, 2016 at 2:21 PM, Paresh Shah <Pa...@lifelock.com> wrote:
> I did not see the option to pick the port when dragging the RPG. This is
> no longer a problem.
>
>
> On 1/21/16, 10:10 AM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>
>>To clarify I do see the ports in the RPG but am not able to turn them
>>“On”. That option is only available for the first in the list.
>>
>>Paresh
>>
>>On 1/21/16, 9:55 AM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>>
>>>I¹m not sure where I would see the ports being called remote group ports.
>>>Using the UI I picked the Input Port on to the canvas at the root level
>>>and am able to see one of them successfully in the RemoteProcessorGroup.
>>>Also I do not see any place where I can set the authorization level.
>>>
>>>
>>>
>>>On 1/21/16, 9:50 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>>
>>>>Paresh,
>>>>
>>>>Screenshots through the apache mailing lists require pretty specific
>>>>delivery mechanism which honestly I don't know. So...best to find a
>>>>way to link to screenshots or to put them in a JIRA.
>>>>
>>>>When you create InputPorts at the root group level they become
>>>>available as ports that another authorized system can see. If they
>>>>are not at the root group level or if they are not authorized to be
>>>>seen by the other system they will not show up in the list.
>>>>
>>>>Can you confirm that these are remote group ports?
>>>>
>>>>Thanks
>>>>Joe
>>>>
>>>>On Thu, Jan 21, 2016 at 12:48 PM, Paresh Shah <Pa...@lifelock.com>
>>>>wrote:
>>>>> I have created different set of InputPorts for the different
>>>>>pipelines.
>>>>>But
>>>>> when I see the list of InputPorts in the RPG I do not see option to
>>>>>pick
>>>>> other ports except the first one in the list.
>>>>>
>>>>> I have attached the screeshots
>>>>>
>>>>>
>>>>> ________________________________
>>>>> The information contained in this transmission may contain privileged
>>>>>and
>>>>> confidential information. It is intended only for the use of the
>>>>>person(s)
>>>>> named above. If you are not the intended recipient, you are hereby
>>>>>notified
>>>>> that any review, dissemination, distribution or duplication of this
>>>>> communication is strictly prohibited. If you are not the intended
>>>>>recipient,
>>>>> please contact the sender by reply email and destroy all copies of the
>>>>> original message.
>>>>> ________________________________
>>>
>>
>>________________________________
>> The information contained in this transmission may contain privileged
>>and confidential information. It is intended only for the use of the
>>person(s) named above. If you are not the intended recipient, you are
>>hereby notified that any review, dissemination, distribution or
>>duplication of this communication is strictly prohibited. If you are not
>>the intended recipient, please contact the sender by reply email and
>>destroy all copies of the original message.
>>________________________________
>
> ________________________________
> The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
> ________________________________
Re: Unable to pick different input ports in the RemoteProcessorGroup
Posted by Paresh Shah <Pa...@lifelock.com>.
I did not see the option to pick the port when dragging the RPG. This is
no longer a problem.
On 1/21/16, 10:10 AM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>To clarify I do see the ports in the RPG but am not able to turn them
>“On”. That option is only available for the first in the list.
>
>Paresh
>
>On 1/21/16, 9:55 AM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>
>>I¹m not sure where I would see the ports being called remote group ports.
>>Using the UI I picked the Input Port on to the canvas at the root level
>>and am able to see one of them successfully in the RemoteProcessorGroup.
>>Also I do not see any place where I can set the authorization level.
>>
>>
>>
>>On 1/21/16, 9:50 AM, "Joe Witt" <jo...@gmail.com> wrote:
>>
>>>Paresh,
>>>
>>>Screenshots through the apache mailing lists require pretty specific
>>>delivery mechanism which honestly I don't know. So...best to find a
>>>way to link to screenshots or to put them in a JIRA.
>>>
>>>When you create InputPorts at the root group level they become
>>>available as ports that another authorized system can see. If they
>>>are not at the root group level or if they are not authorized to be
>>>seen by the other system they will not show up in the list.
>>>
>>>Can you confirm that these are remote group ports?
>>>
>>>Thanks
>>>Joe
>>>
>>>On Thu, Jan 21, 2016 at 12:48 PM, Paresh Shah <Pa...@lifelock.com>
>>>wrote:
>>>> I have created different set of InputPorts for the different
>>>>pipelines.
>>>>But
>>>> when I see the list of InputPorts in the RPG I do not see option to
>>>>pick
>>>> other ports except the first one in the list.
>>>>
>>>> I have attached the screeshots
>>>>
>>>>
>>>> ________________________________
>>>> The information contained in this transmission may contain privileged
>>>>and
>>>> confidential information. It is intended only for the use of the
>>>>person(s)
>>>> named above. If you are not the intended recipient, you are hereby
>>>>notified
>>>> that any review, dissemination, distribution or duplication of this
>>>> communication is strictly prohibited. If you are not the intended
>>>>recipient,
>>>> please contact the sender by reply email and destroy all copies of the
>>>> original message.
>>>> ________________________________
>>
>
>________________________________
> The information contained in this transmission may contain privileged
>and confidential information. It is intended only for the use of the
>person(s) named above. If you are not the intended recipient, you are
>hereby notified that any review, dissemination, distribution or
>duplication of this communication is strictly prohibited. If you are not
>the intended recipient, please contact the sender by reply email and
>destroy all copies of the original message.
>________________________________
________________________________
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
Re: Unable to pick different input ports in the RemoteProcessorGroup
Posted by Paresh Shah <Pa...@lifelock.com>.
To clarify I do see the ports in the RPG but am not able to turn them
“On”. That option is only available for the first in the list.
Paresh
On 1/21/16, 9:55 AM, "Paresh Shah" <Pa...@lifelock.com> wrote:
>I¹m not sure where I would see the ports being called remote group ports.
>Using the UI I picked the Input Port on to the canvas at the root level
>and am able to see one of them successfully in the RemoteProcessorGroup.
>Also I do not see any place where I can set the authorization level.
>
>
>
>On 1/21/16, 9:50 AM, "Joe Witt" <jo...@gmail.com> wrote:
>
>>Paresh,
>>
>>Screenshots through the apache mailing lists require pretty specific
>>delivery mechanism which honestly I don't know. So...best to find a
>>way to link to screenshots or to put them in a JIRA.
>>
>>When you create InputPorts at the root group level they become
>>available as ports that another authorized system can see. If they
>>are not at the root group level or if they are not authorized to be
>>seen by the other system they will not show up in the list.
>>
>>Can you confirm that these are remote group ports?
>>
>>Thanks
>>Joe
>>
>>On Thu, Jan 21, 2016 at 12:48 PM, Paresh Shah <Pa...@lifelock.com>
>>wrote:
>>> I have created different set of InputPorts for the different pipelines.
>>>But
>>> when I see the list of InputPorts in the RPG I do not see option to
>>>pick
>>> other ports except the first one in the list.
>>>
>>> I have attached the screeshots
>>>
>>>
>>> ________________________________
>>> The information contained in this transmission may contain privileged
>>>and
>>> confidential information. It is intended only for the use of the
>>>person(s)
>>> named above. If you are not the intended recipient, you are hereby
>>>notified
>>> that any review, dissemination, distribution or duplication of this
>>> communication is strictly prohibited. If you are not the intended
>>>recipient,
>>> please contact the sender by reply email and destroy all copies of the
>>> original message.
>>> ________________________________
>
________________________________
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
Re: Unable to pick different input ports in the RemoteProcessorGroup
Posted by Paresh Shah <Pa...@lifelock.com>.
I¹m not sure where I would see the ports being called remote group ports.
Using the UI I picked the Input Port on to the canvas at the root level
and am able to see one of them successfully in the RemoteProcessorGroup.
Also I do not see any place where I can set the authorization level.
On 1/21/16, 9:50 AM, "Joe Witt" <jo...@gmail.com> wrote:
>Paresh,
>
>Screenshots through the apache mailing lists require pretty specific
>delivery mechanism which honestly I don't know. So...best to find a
>way to link to screenshots or to put them in a JIRA.
>
>When you create InputPorts at the root group level they become
>available as ports that another authorized system can see. If they
>are not at the root group level or if they are not authorized to be
>seen by the other system they will not show up in the list.
>
>Can you confirm that these are remote group ports?
>
>Thanks
>Joe
>
>On Thu, Jan 21, 2016 at 12:48 PM, Paresh Shah <Pa...@lifelock.com>
>wrote:
>> I have created different set of InputPorts for the different pipelines.
>>But
>> when I see the list of InputPorts in the RPG I do not see option to pick
>> other ports except the first one in the list.
>>
>> I have attached the screeshots
>>
>>
>> ________________________________
>> The information contained in this transmission may contain privileged
>>and
>> confidential information. It is intended only for the use of the
>>person(s)
>> named above. If you are not the intended recipient, you are hereby
>>notified
>> that any review, dissemination, distribution or duplication of this
>> communication is strictly prohibited. If you are not the intended
>>recipient,
>> please contact the sender by reply email and destroy all copies of the
>> original message.
>> ________________________________
________________________________
The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
Re: Unable to pick different input ports in the RemoteProcessorGroup
Posted by Joe Witt <jo...@gmail.com>.
Paresh,
Screenshots through the apache mailing lists require pretty specific
delivery mechanism which honestly I don't know. So...best to find a
way to link to screenshots or to put them in a JIRA.
When you create InputPorts at the root group level they become
available as ports that another authorized system can see. If they
are not at the root group level or if they are not authorized to be
seen by the other system they will not show up in the list.
Can you confirm that these are remote group ports?
Thanks
Joe
On Thu, Jan 21, 2016 at 12:48 PM, Paresh Shah <Pa...@lifelock.com> wrote:
> I have created different set of InputPorts for the different pipelines. But
> when I see the list of InputPorts in the RPG I do not see option to pick
> other ports except the first one in the list.
>
> I have attached the screeshots
>
>
> ________________________________
> The information contained in this transmission may contain privileged and
> confidential information. It is intended only for the use of the person(s)
> named above. If you are not the intended recipient, you are hereby notified
> that any review, dissemination, distribution or duplication of this
> communication is strictly prohibited. If you are not the intended recipient,
> please contact the sender by reply email and destroy all copies of the
> original message.
> ________________________________