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 [email protected] [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Dec 10, 2019, at 1:51 PM, sanjeet rath <[email protected]> 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
