Re: Closing in on a NiFi 1.2.0 release?

Sweet! I'll take that deal all day. Thanks Bryan! On Wed, Mar 22, 2017 at 8:26 PM, Bryan Bende wrote: > Joe, > > As of today I believe the PR for NIFI-3380 (component versioning) should > address all of the code review feedback and is in a good place. > > Would like to run

Re: Closing in on a NiFi 1.2.0 release?

Joe, As of today I believe the PR for NIFI-3380 (component versioning) should address all of the code review feedback and is in a good place. Would like to run through a few more tests tomorrow, and baring any additional feedback from reviewers, we could possibly merge that tomorrow. That PR

Re: FetchS3Object leak

Hi James, Sorry - you are right. I searched for close and didn't notice it was in a try with resources block. The weirder thing is we only allow a single task to schedule at a time, which lead me to think it was leaking resources. I'll continue investigating and see if I can find out what's

Re: FetchS3Object leak

David, Can you clarify which part of the FetchS3Object code looks problematic to you? From a quick look, I found one use of S3Object in FetchS3Object.java, line ~106: try (final S3Object s3Object = client.getObject(request)) { flowFile =

FetchS3Object leak

Greetings, In investigating a connection pool issue we were having during development, I was checking the FetchS3Object code to see how it reads content from S3. I don't see a close()

Re: NIFI Jira rights

Thank you On March 22, 2017 at 13:12:11, Joe Witt (joe.w...@gmail.com) wrote: Otto I've added you to the contributors list on the nifi JIRA so you should be all set there. Thanks Joe On Wed, Mar 22, 2017 at 1:05 PM, Otto Fowler wrote: > Would it be possible to get

Re: Error in "PutHiveQL" processor

Anshuman, According to [1], it looks like CDH 5.10 also uses an Apache Hive 1.1.0 baseline, and looking through the changes [2] I didn't see anything related to the client_protocol field being added. You are right that ExecuteProcess should also work with a beeline command, the major difference

Re: NIFI Jira rights

Otto I've added you to the contributors list on the nifi JIRA so you should be all set there. Thanks Joe On Wed, Mar 22, 2017 at 1:05 PM, Otto Fowler wrote: > Would it be possible to get rights to the NIFI Jira project, such that I > can assign issues to myself? I

NIFI Jira rights

Would it be possible to get rights to the NIFI Jira project, such that I can assign issues to myself? I already have these rights as a committer for the Metron project, and would like to assign issues I enter and plan on working on to myself, such as

Re: Error in "PutHiveQL" processor

Anshuman, The Hive processors use Apache Hive 1.2.0, which is not compatible with Hive 1.1.0 and is thus a known issue against clusters that use Hive 1.1.0 such as CDH 5.9. Unfortunately there were API/code changes between Hive 1.1.0 and Hive 1.2.0, which means there is no simple workaround with

Error in "PutHiveQL" processor

Hello everyone, I am trying to use this "PutHiveQL" processor. However no luck with the connection string, seems like I am missing out on something. I am getting an error like "*Required field 'client_protocol' is unset!*" Please find the attachments for the error message and also config

Re: Regarding changes in Apache Nifi

Hey Dave, Bryan, Thanks for your help. We were able to change the UI. Here are some screenshots of what we did so far. Regards, Sunil Neurgaonkar On Thu, Mar 16, 2017 at 7:55 PM, Dave Hirko wrote: > We’ve built custom, UI abstractions on top of Nifi using the REST API’s >