[DISCUSS} Closing in on a NiFi 1.4.0 release?

All, On the dev and users lists there have been some questions about when the next release of NiFi would be. I would like perform RM duties, and get things started on identifying what the community would like to include in the release of NiFi 1.4.0 that has not already been reviewed and

Re: Duplicated processors when using nifi processors dependency

Sorry if this duplicates, I sent from the wrong address the first time. I’ve opened a PR on GitHub for this issue: https://github.com/apache/ nifi/pull/2140 Let me know if there’s any other follow up I need to do; I’d love to see this get in for 1.4.0. Christopher On 2017-05-22 06:16, Bryan

Re: Url encoding with S3 processors

Thanks James, I wasn't aware of the urlDecode() EL expression. On Sun, Sep 10, 2017 at 5:31 PM, James Wing wrote: > Joe, > > The good news is that you can use expression language directly in > FetchS3Object's Object Key property to decode your keys. For example, > >

Re: Url encoding with S3 processors

Joe, The good news is that you can use expression language directly in FetchS3Object's Object Key property to decode your keys. For example, ${filename:urlDecode()} However, I'm not sure that could be done without you specifying that the key should be decoded. As I understand it, the following