@vystar  Considering the breaking changes that are part of Apache NiFi 2.0/1, there is considerably more work in preparing for an upgrade to the that new major release.  So I would recommend upgrading to the latest offering in the Apache NiFi 1.x branch.   You'll want to review all the release notes from 1.13 to the latest release: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes/#ReleaseNotes-Version1.12.0 You'll want to pay close attention to any mentions of components being moved to optional build profiles.  This means that these nars and the components they contain are no longer include with the Apache NiFi download and if needed must be downloaded form Maven Central and manually added to NiFi.   Deprecated components still exist in the Download, but will not exist in NiFi 2.x releases. Make sure to maintain a copy of your flow.xml.gz/flow.json.gz (newer releases).  The newer Apache NiFi 1.x load a flow.json.gz instead of the older flow.xml.gz on startup.  However, in the absence of a flow.json.gz and the presence of flow.xml.gz, NiFi 1.x will load from the flow.xml.gz and produce the new flow.json.gz. After upgrade, you'll still need to review your dataflows.  There are some bad practices that are now blocked by Apache NiFi that may leave some components invalid until manual action is taken to resolve the bad configuration (such as using "primary node" execution on any processor that has an inbound connection). As far as FlowFile distribution, do it early in your dataflows as possible. Utilize list/fetch still processors instead of get style. (Example: use ListSFTP and FetchSFTP in place of GetSFTP.  This allows you to load-balance the 0 byte listed files before the content is fetched for the files). Other options like Remote Process Groups can be used (they come with some overhead, but do some target NiFi Cluster load based distribution when dealing with large volumes of FlowFiles.  Not so great for low volumes.).   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 more

Hi All, It was issue related to config setting. After setting the environment properly issue got resolved. It seems due to some misconfiguration of JAAS and krb5.conf. Following below blog has resolved the issue http://shantanu01.blogspot.com/2020/06/how-to-setup-beeline-on-linux-for.html ... View more

@azrulafiq901 Thank you for bringing this to our community.  Did you get help on this? If not, You may also follow: [0a] Managing Licenses: https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/managing-clusters/topics/cm-managing-licenses.html I highly recommend you discussing potential partnership with our Sales Executives. https://www.cloudera.com/contact-sales.html If you still need help, Please feel free to update this thread, so I can have our team approach you on your behalf. I hope this helps.   If this answers your question, You may mark this answer as Accept as Solution. You can also say thanks by clicking on the thumbs up button.   V ... View more