Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Who agreed with this solution

avatar
author-rank MattWho author-rank
Master Mentor

Created ‎05-23-2024 05:57 AM

@alan18080 

The Postgres DB only holds metadata and does not contain the actual datflow in NiFi-registry.  The version controlled dataflows are stored in the configured FlowPersistenceProvider.   So if you are not preserving the actual flow contents, then the metadata loaded from your postgresSQL will not find it after redeployment.

I would also recommend upgrading your NiFi-Registry and NiFi versions. NiFi-Registry is going on 4 years old.

Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt





View solution in original post

4,493
1
Who agreed with this solution