@arutkwccu  Yes, the added ParquetReader will be available to the record processors that utilize record reader or writer. There is not a lot involved in this process. Simply download these two nar files and place them in the NiFi extensions folder owned by NiFi service user. NiFi takes care of the rest. I added these two nars to my 2.0.0-M1 installation to show you that it works here: If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@arutkwccu @joseomjr  NiFi components evolve from release to release.  as part of their evolution the components may have default properties added or removed. That is the case here with invokeHTTP processor.  The property "Proxy Type" idd exist as a property in Apache NiFi 1.24 invokeHTTP processor and had a default value of "http". This property was removed in Apache NIFi 2.0.0-M1 invokeHTTP processor. In this specific example: - Earlier version of Apache NIFi 1.x invokeHTTP processor supported configuring proxy properties directly in the processor.  Later version of Apache NiFi allowed those same configuration to be abstracted to a StandardProxyConfigurationService controller service (for ease of reuse), but also kept the original direct properties in the processor to avoid upgrade issues for user upgrading within a minor release change.  As Apache NiFi 2.0.0-M1 is a major release, clean-up is happening here to remove the deprecated config methods for the newer controller service config method. When a NiFi loads the flow.json.gz from another NiFi it loads the same class and reads in all the configured properties.  For any configured property where the current version does not have the same property, the property is added as a custom dynamic property.  This may render your component invalid until manual correction is made (in your case deleting this dynamic property).   Apache NiFi has always functioned in this way and it is not a bug.  It is not possible for NiFi framework to know what "dynamic" properties should or should not be added to component, it simply reads what is found in the flow.json.gz being loaded.  Validating your dataflows post any upgrade (not just major version changes like Apache NiFi 1.x to 2.x) is a necessary step. This specific migration is mentioned in the Migrating Deprecated Components and Features guide. You'll know right away if a property is not a default property but rather a "dynamic" custom property when you see it.  Only dynamic properties will present the trashcan icon to the right of it allowing you to delete it. Hope this adds clarity here. If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Mat ... View more

@arutkwccu  The parquet components were not "deprecated", they were moved out of the default distribution via https://issues.apache.org/jira/browse/NIFI-12282 Apache limits the max size of the project and at times some nars need to be moved out of the distribution to avoid exceeding that max allowed project download size or components less commonly used may be moved out.  Does not mean that these components ate no longer being contributed to or updated with the newer NiFi release versions.  It does mean however that you will need to manually download the nifi-parquet-nar and any dependency nar(s) it needs that are not already included in your NiFi distribution. You can download nars directly from maven central. Here is the link to the maven central for the nifi-parquet-nar: https://central.sonatype.com/artifact/org.apache.nifi/nifi-parquet-nar/overview If you look at the "Dependencies" tab, you'll see that there is a dependecy on another nar (nifi-hadoop-libraries-nar). Neither of these nars are inlcuded in the default Apache NiFi 2.0.-M1 release. The simplest way to add these nars to your NiFi is to download them into the <path-toNiFi>/extensions/" folder. NiFi will auto-load nars placed on this folder without any need for a NiFi restart. You can find the nars by clicking on the "versions" tab for each required nar and clciking on "Browse" next to the NiFi version you want the nar for. Here are the direct links for the two nars you need for parquet: nifi-parquet-nar - https://repo1.maven.org/maven2/org/apache/nifi/nifi-parquet-nar/2.0.0-M1/nifi-parquet-nar-2.0.0-M1.nar nifi-hadoop-libraries-nar - https://repo1.maven.org/maven2/org/apache/nifi/nifi-hadoop-libraries-nar/2.0.0-M1/nifi-hadoop-libraries-nar-2.0.0-M1.nar If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more