NiFi doesn't seem to take -F as an input while invoking the following request: curl -X POST "http://ipaddress:port/api/" -H "accept: application/json" -H "Content-Type: multipart/form-data" -F "pdf_file=@sample.pdf;type=application/pdf" It seems to me that it is by default requesting in this format: curl -X POST "http://ipaddress:port/api/" -H "accept: application/json" -H "Content-Type: multipart/form-data" -d "pdf_file=@sample.pdf;type=application/pdf" Sending raw data instead of form data. The API hence responds with error saying: "400 Bad Request: The browser (or proxy) sent a request that this server could not understand." Whereas Using PostHttp: setting the same URL and content-type as application/form-data gives me 500 internal server error server logs: readv() failed (104: Connection reset by peer) while reading upstream ... View more

I am able to get the details of the prefix I need to recursively list only after execution of four initial processors. Since I can not use ListS3 processor in the middle of the flow (It does not take an incoming relationship). How can I list the prefix in S3 recursively. I fetch a json file from S3 bucket that contains the prefix information. This prefix changes daily. Then I need to list the prefix recursively. aws s3 ls s3://{Bucket Name}/{prefix}/ --recursive ... View more

I use JSON Paths as attributes to nifi flowfiles (of JSON mime type). I want to evaluate these JSON Path over the content of the flowfiles but I can't use Evaluate JSON path processor as it does not support expression language. How can I do this as I can't hard code the JSON Paths in the processor, they are varying file to file. ... View more