You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by sanjeet rath <ra...@gmail.com> on 2019/12/10 12:51:36 UTC
Clarification regarding NiFi registry
Hi ,
I just have confusion but no where i am finding a proper documentation
regarding how nifi nodes intigrates with nifi registry. means internally
how it works.as per the code , the node calls API to get the registry
details and storing the entiry in RegistryDTO object.
So my question is , Is it storing in persistant storage like db or in
memory.
If it stores in memory, then when we restarting the nifi application how it
again connect to registry , is it again call the API .
I am sorry if my understanding is wrong.
please let me know.
Thanks in advance
Regards,
Sanjeet
Re: Clarification regarding NiFi registry
Posted by Bryan Bende <bb...@gmail.com>.
It is stored in flow.xml.gz
On Tue, Dec 10, 2019 at 10:00 AM sanjeet rath <ra...@gmail.com> wrote:
>
> Hi Bryan,
>
> I am facing the issue in 1.8 version
> Currently I am dubugging the nifi code to figuring it out.
> In the mean time could u please tell me when we add the registry name and URL in Nifi settings UI, actually in which location localy this value stored.means the persistant storage in local node.
>
> Regards,
> Sanjeet
>
> On Tue, 10 Dec, 2019, 8:18 PM Bryan Bende, <bb...@gmail.com> wrote:
>>
>> One other use has reported this, but I have been unable to reproduce it:
>>
>> https://issues.apache.org/jira/browse/NIFI-6767
>>
>> Can you come up with steps that someone could take to reproduce the problem?
>>
>> Starting with step 1 - download version xyz of Nifi
>>
>> On Tue, Dec 10, 2019 at 9:30 AM sanjeet rath <ra...@gmail.com> wrote:
>> >
>> > Thanks Andy for this quick response.
>> > Actually i am going in details because while restarting nifi i am getting incorrect info in nifi settings -- >registry location -- >location as
>> > https:// null or sometimes
>> > https:// host -1
>> >
>> > is there any suggestions for this issue.
>> > thanks ,
>> > sanjeet
>> >
>> >
>> >
>> > On Tue, 10 Dec, 2019, 7:22 PM Andy LoPresto, <al...@apache.org> wrote:
>> >>
>> >> The NiFi Registry documentation [1] explains the interaction between the two services in more detail, but the basic process is that a Registry Client is configured in NiFi which contains the information necessary for NiFi to connect to the registry. Assets (currently flow definitions or extensions) are persisted or retrieved to/from the registry instance over HTTP(S).
>> >>
>> >> In NiFi Registry, those assets are persisted in either Git or a relational database configured locally.
>> >>
>> >> When NiFi restarts, the flow controller (global scheduling system) uses the configured Registry Client to connect to the registry instance as necessary.
>> >>
>> >> [1] https://nifi.apache.org/docs/nifi-registry-docs/index.html
>> >>
>> >>
>> >> Andy LoPresto
>> >> alopresto@apache.org
>> >> alopresto.apache@gmail.com
>> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>> >>
>> >> On Dec 10, 2019, at 1:51 PM, sanjeet rath <ra...@gmail.com> wrote:
>> >>
>> >> Hi ,
>> >>
>> >> I just have confusion but no where i am finding a proper documentation regarding how nifi nodes intigrates with nifi registry. means internally how it works.as per the code , the node calls API to get the registry details and storing the entiry in RegistryDTO object.
>> >>
>> >> So my question is , Is it storing in persistant storage like db or in memory.
>> >> If it stores in memory, then when we restarting the nifi application how it again connect to registry , is it again call the API .
>> >>
>> >> I am sorry if my understanding is wrong.
>> >> please let me know.
>> >>
>> >> Thanks in advance
>> >> Regards,
>> >> Sanjeet
>> >>
>> >>
Re: Clarification regarding NiFi registry
Posted by sanjeet rath <ra...@gmail.com>.
Hi Bryan,
I am facing the issue in 1.8 version
Currently I am dubugging the nifi code to figuring it out.
In the mean time could u please tell me when we add the registry name and
URL in Nifi settings UI, actually in which location localy this value
stored.means the persistant storage in local node.
Regards,
Sanjeet
On Tue, 10 Dec, 2019, 8:18 PM Bryan Bende, <bb...@gmail.com> wrote:
> One other use has reported this, but I have been unable to reproduce it:
>
> https://issues.apache.org/jira/browse/NIFI-6767
>
> Can you come up with steps that someone could take to reproduce the
> problem?
>
> Starting with step 1 - download version xyz of Nifi
>
> On Tue, Dec 10, 2019 at 9:30 AM sanjeet rath <ra...@gmail.com>
> wrote:
> >
> > Thanks Andy for this quick response.
> > Actually i am going in details because while restarting nifi i am
> getting incorrect info in nifi settings -- >registry location -- >location
> as
> > https:// null or sometimes
> > https:// host -1
> >
> > is there any suggestions for this issue.
> > thanks ,
> > sanjeet
> >
> >
> >
> > On Tue, 10 Dec, 2019, 7:22 PM Andy LoPresto, <al...@apache.org>
> wrote:
> >>
> >> The NiFi Registry documentation [1] explains the interaction between
> the two services in more detail, but the basic process is that a Registry
> Client is configured in NiFi which contains the information necessary for
> NiFi to connect to the registry. Assets (currently flow definitions or
> extensions) are persisted or retrieved to/from the registry instance over
> HTTP(S).
> >>
> >> In NiFi Registry, those assets are persisted in either Git or a
> relational database configured locally.
> >>
> >> When NiFi restarts, the flow controller (global scheduling system) uses
> the configured Registry Client to connect to the registry instance as
> necessary.
> >>
> >> [1] https://nifi.apache.org/docs/nifi-registry-docs/index.html
> >>
> >>
> >> Andy LoPresto
> >> alopresto@apache.org
> >> alopresto.apache@gmail.com
> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> >>
> >> On Dec 10, 2019, at 1:51 PM, sanjeet rath <ra...@gmail.com>
> wrote:
> >>
> >> Hi ,
> >>
> >> I just have confusion but no where i am finding a proper documentation
> regarding how nifi nodes intigrates with nifi registry. means internally
> how it works.as per the code , the node calls API to get the registry
> details and storing the entiry in RegistryDTO object.
> >>
> >> So my question is , Is it storing in persistant storage like db or in
> memory.
> >> If it stores in memory, then when we restarting the nifi application
> how it again connect to registry , is it again call the API .
> >>
> >> I am sorry if my understanding is wrong.
> >> please let me know.
> >>
> >> Thanks in advance
> >> Regards,
> >> Sanjeet
> >>
> >>
>
Re: Clarification regarding NiFi registry
Posted by Bryan Bende <bb...@gmail.com>.
One other use has reported this, but I have been unable to reproduce it:
https://issues.apache.org/jira/browse/NIFI-6767
Can you come up with steps that someone could take to reproduce the problem?
Starting with step 1 - download version xyz of Nifi
On Tue, Dec 10, 2019 at 9:30 AM sanjeet rath <ra...@gmail.com> wrote:
>
> Thanks Andy for this quick response.
> Actually i am going in details because while restarting nifi i am getting incorrect info in nifi settings -- >registry location -- >location as
> https:// null or sometimes
> https:// host -1
>
> is there any suggestions for this issue.
> thanks ,
> sanjeet
>
>
>
> On Tue, 10 Dec, 2019, 7:22 PM Andy LoPresto, <al...@apache.org> wrote:
>>
>> The NiFi Registry documentation [1] explains the interaction between the two services in more detail, but the basic process is that a Registry Client is configured in NiFi which contains the information necessary for NiFi to connect to the registry. Assets (currently flow definitions or extensions) are persisted or retrieved to/from the registry instance over HTTP(S).
>>
>> In NiFi Registry, those assets are persisted in either Git or a relational database configured locally.
>>
>> When NiFi restarts, the flow controller (global scheduling system) uses the configured Registry Client to connect to the registry instance as necessary.
>>
>> [1] https://nifi.apache.org/docs/nifi-registry-docs/index.html
>>
>>
>> Andy LoPresto
>> alopresto@apache.org
>> alopresto.apache@gmail.com
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>>
>> On Dec 10, 2019, at 1:51 PM, sanjeet rath <ra...@gmail.com> wrote:
>>
>> Hi ,
>>
>> I just have confusion but no where i am finding a proper documentation regarding how nifi nodes intigrates with nifi registry. means internally how it works.as per the code , the node calls API to get the registry details and storing the entiry in RegistryDTO object.
>>
>> So my question is , Is it storing in persistant storage like db or in memory.
>> If it stores in memory, then when we restarting the nifi application how it again connect to registry , is it again call the API .
>>
>> I am sorry if my understanding is wrong.
>> please let me know.
>>
>> Thanks in advance
>> Regards,
>> Sanjeet
>>
>>
Re: Clarification regarding NiFi registry
Posted by sanjeet rath <ra...@gmail.com>.
Thanks Andy for this quick response.
Actually i am going in details because while restarting nifi i am getting
incorrect info in nifi settings -- >registry location -- >location as
https:// null or sometimes
https:// host -1
is there any suggestions for this issue.
thanks ,
sanjeet
On Tue, 10 Dec, 2019, 7:22 PM Andy LoPresto, <al...@apache.org> wrote:
> The NiFi Registry documentation [1] explains the interaction between the
> two services in more detail, but the basic process is that a Registry
> Client is configured in NiFi which contains the information necessary for
> NiFi to connect to the registry. Assets (currently flow definitions or
> extensions) are persisted or retrieved to/from the registry instance over
> HTTP(S).
>
> In NiFi Registry, those assets are persisted in either Git or a relational
> database configured locally.
>
> When NiFi restarts, the flow controller (global scheduling system) uses
> the configured Registry Client to connect to the registry instance as
> necessary.
>
> [1] https://nifi.apache.org/docs/nifi-registry-docs/index.html
>
>
> Andy LoPresto
> alopresto@apache.org
> *alopresto.apache@gmail.com <al...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Dec 10, 2019, at 1:51 PM, sanjeet rath <ra...@gmail.com> wrote:
>
> Hi ,
>
> I just have confusion but no where i am finding a proper documentation
> regarding how nifi nodes intigrates with nifi registry. means internally
> how it works.as per the code , the node calls API to get the registry
> details and storing the entiry in RegistryDTO object.
>
> So my question is , Is it storing in persistant storage like db or in
> memory.
> If it stores in memory, then when we restarting the nifi application how
> it again connect to registry , is it again call the API .
>
> I am sorry if my understanding is wrong.
> please let me know.
>
> Thanks in advance
> Regards,
> Sanjeet
>
>
>
Re: Clarification regarding NiFi registry
Posted by Andy LoPresto <al...@apache.org>.
The NiFi Registry documentation [1] explains the interaction between the two services in more detail, but the basic process is that a Registry Client is configured in NiFi which contains the information necessary for NiFi to connect to the registry. Assets (currently flow definitions or extensions) are persisted or retrieved to/from the registry instance over HTTP(S).
In NiFi Registry, those assets are persisted in either Git or a relational database configured locally.
When NiFi restarts, the flow controller (global scheduling system) uses the configured Registry Client to connect to the registry instance as necessary.
[1] https://nifi.apache.org/docs/nifi-registry-docs/index.html <https://nifi.apache.org/docs/nifi-registry-docs/index.html>
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Dec 10, 2019, at 1:51 PM, sanjeet rath <ra...@gmail.com> wrote:
>
> Hi ,
>
> I just have confusion but no where i am finding a proper documentation regarding how nifi nodes intigrates with nifi registry. means internally how it works.as <http://works.as/> per the code , the node calls API to get the registry details and storing the entiry in RegistryDTO object.
>
> So my question is , Is it storing in persistant storage like db or in memory.
> If it stores in memory, then when we restarting the nifi application how it again connect to registry , is it again call the API .
>
> I am sorry if my understanding is wrong.
> please let me know.
>
> Thanks in advance
> Regards,
> Sanjeet