The parquet data itself has the schema, and your writer should be configured with schema access strategy to inherit schema from reader. Schema Access Strategyinherit-record-schema Use 'Schema Name' Property Inherit Record Schema Use 'Schema Text' Property This will produce a flow file with many records. If you need 1 record per flow file then you would use SplitRecord after this, however generally it is better to keep many records together. ... View more

FetchParquet has a property for a record writer... when it fetches the parquet, it will read it record by record using Parquet's Avro reader, and then pass each record to the configured writer. So if you configured it with a JSON record writer, then the resulting flow file that is fetched will contain JSON. If you wanted to fetch raw parquet then you wouldn't use FetchParquet, but would instead just use FetchHDFS which fetches bytes unmodified. ... View more

https://pierrevillard.com/2017/01/24/integration-of-nifi-with-ldap/ https://ijokarumawak.github.io/nifi/2016/11/15/nifi-auth/ https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#ldap_login_identity_provider ... View more

Just wanted to add some more info... The Parquet Java API only allows reading and writing to and from Hadoop's Filesystem API, this is why NiFi currently can't provide a standard record reader and writer because those require reading and writing to Java's InputStream and OutputStream, which Parquet doesn't provide. So PutParquet can be configured with a record reader to handle any incoming data, and then converts it to Parquet and writes to HDFS, basically it has a record writer encapsulated in it that can only write to HDFS. FetchParquet does the reverse where it can read Parquet files from HDFS and then can be configured with a record writer to write them out as any form, in your case CSV. You can always create core-site.xml with a local filesystem to trick the Parquet processors into using local disk instead of HDFS. ... View more

If ListFTP is showing an error in the UI then that error message is in nifi-app.log somewhere, please provide the full stacktrace that goes with that error. ... View more

When you say it is "not working", what exactly is happening? There can only really be three possible outcomes... a) it fetched successfully b) it did not fetch successfully and there is a red error on the processor in the UI, and an error in nifi-app.log c) it is stuck connecting and there is a little number icon in the top-right of the processor which shows that 1 thread is still running trying to execute Which of these choices describes the result? ... View more