Re: FetchS3Object fails to fetch small files from S3

2021-08-17 Thread Denes Arvay
Joey, I was able to reproduce the issue with a 0 byte file. Reverting the commit you were referring to ([1]) fixes the problem. Denes [1] https://github.com/apache/nifi/commit/0ed35345245da057400a7d875e47f57bc2d3794d On Tue, Aug 17, 2021 at 8:12 AM Joey Frazee wrote: > Vibhath, there was a

Re: Unable to send JSON to BigQuery

2019-07-03 Thread Denes Arvay
JIRA (I already have access to) ? > Le 03/07/2019 à 11:28, Denes Arvay a écrit : > > Hi Nicolas, > > It seems that NiFi expects to have the "mode" field being present, even > though based on the BigQuery doc [1] it's optional. > I'd suggest trying adding it to every na

Re: Unable to send JSON to BigQuery

2019-07-03 Thread Denes Arvay
Hi Nicolas, It seems that NiFi expects to have the "mode" field being present, even though based on the BigQuery doc [1] it's optional. I'd suggest trying adding it to every name-type pair with its default value "NULLABLE". (i.e. { "name": "Consent", "type": "record", *"mode": "NULLABLE"*,

Re: Problem with property descriptor in InvokeScriptedProcessor

2019-03-21 Thread Denes Arvay
Hi Elemir, Setting the log level to DEBUG outputs more details, it seems the cause of the exception is the following: javax.script.ScriptException: NameError: global name 'StandardValidators' is not defined in

Re: Can't trim leading whitespaces with UpdateRecord

2019-03-19 Thread Denes Arvay
Hi Eric, I did some quick tests, replaceRegex works well for me. The regex patterns should behave as expected (see: https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/functions/ReplaceRegex.java#L49-L49), I don't see any reason why

Re: Processor(s) to monitor for new subdirectories?

2019-03-11 Thread Denes Arvay
Hi Jim, I suppose you want to monitor the newly created but still empty subdirectories, right? ListFile doesn't list those and I'm not aware of any processor for this purpose. I created a quick patch for ListFile, feel free to use it as is or as a starting point:

Re: Invalid CORS request error on NiFi v1.8.0 and 1.9.0 behind nginx

2019-02-28 Thread Denes Arvay
is intending to do the action. > > More info available here: > https://security.stackexchange.com/questions/191737/how-do-cors-proxy-websites-work > > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6

Re: Invalid CORS request error on NiFi v1.8.0 and 1.9.0 behind nginx

2019-02-26 Thread Denes Arvay
rization. This could result in RCE. Denes’ suggestion about rewriting > the Origin header in your proxy should work. > > [1] https://nifi.apache.org/security.html#CVE-2018-17195 > > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70E

Re: Invalid CORS request error on NiFi v1.8.0 and 1.9.0 behind nginx

2019-02-22 Thread Denes Arvay
at 11:00 AM Denes Arvay wrote: > Hi Elemir, > > I was able to reproduce your issue with a simple nginx-NiFi setup, both > running on localhost. > My guess is that the cause is that POST is missing from allowed methods > list from the /process-groups/*/templates/upload path [1].

Re: Invalid CORS request error on NiFi v1.8.0 and 1.9.0 behind nginx

2019-02-22 Thread Denes Arvay
Hi Elemir, I was able to reproduce your issue with a simple nginx-NiFi setup, both running on localhost. My guess is that the cause is that POST is missing from allowed methods list from the /process-groups/*/templates/upload path [1]. The commit which introduced this change explicitly states