Created on 06-24-2022 08:26 AM - edited 06-24-2022 08:28 AM
Created 06-29-2022 12:17 PM
@ajignacio
You should carefully read all the migration guidance leading up to 1.16 starting with:
Migrating from 1.x.x to 1.10.0
Take special note of:
1. Any nars that may have been removed and make sure your dataflows are not using any processors from those removed nars.
2. Any reported changes to specific components you may use in your dataflows.
3. Check that your dataflow does not have any processors with inbound connection scheduled to execute on "Primary Node" only (small P in upper left corner of processor).
4. Take note of migration step involving sensitive .props.key. If you had not set one previously, you may want to use the nifi toolkit to create a new user defined one and re-encrypt the sensitive property values in the flow.xml.gz using that new sensitive props key.
5. Make sure you upgrade to a java 8 NiFi 1.16 supported Java version before migration.
NOTE: While Apache NiFi has limits on the maximum size fo the service forcing deprecation of older nars, Cloudera's CFM distributions of Apache NiFi do not and include almost all Apache nars in addition to Cloudera specific nars.
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
Created 06-24-2022 01:39 PM
If you plan upgrade to Cloudera Flow Management 2.1.4, which includes NiFi 1.16, you can follow the migration Paths that are listed in the next document:
https://docs.cloudera.com/cfm/2.1.4/upgrade-paths/topics/cfm-upgrade-paths.html
Created 06-29-2022 12:17 PM
@ajignacio
You should carefully read all the migration guidance leading up to 1.16 starting with:
Migrating from 1.x.x to 1.10.0
Take special note of:
1. Any nars that may have been removed and make sure your dataflows are not using any processors from those removed nars.
2. Any reported changes to specific components you may use in your dataflows.
3. Check that your dataflow does not have any processors with inbound connection scheduled to execute on "Primary Node" only (small P in upper left corner of processor).
4. Take note of migration step involving sensitive .props.key. If you had not set one previously, you may want to use the nifi toolkit to create a new user defined one and re-encrypt the sensitive property values in the flow.xml.gz using that new sensitive props key.
5. Make sure you upgrade to a java 8 NiFi 1.16 supported Java version before migration.
NOTE: While Apache NiFi has limits on the maximum size fo the service forcing deprecation of older nars, Cloudera's CFM distributions of Apache NiFi do not and include almost all Apache nars in addition to Cloudera specific nars.
If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.
Thank you,
Matt
Created 09-01-2022 03:22 AM
Thank you Matt sorry for the super delay response but it's very helpful