Re: [DISCUSS] On HBase client retries (NIFI-6197)

2020-02-19 Thread Lars Francke
That's what I suggested[1] and Bryan rejected[2] [1] [2] On Wed, Feb 19, 2020 at 4:29 PM Josh Elser wrote: > Thanks for sharing the code, Bryan! I lazily did not

Re: [VOTE] Release Apache NiFi 1.11.2 (rc1)

2020-02-19 Thread Joe Witt
+1 (binding) On Wed, Feb 19, 2020 at 5:48 AM Marton Szasz wrote: > +1 (non-binding) > Verified signature, checksum, git commit ID, LICENSE/README/NOTICE files. > Built, successfully ran a simple flow. > > On Wed, 19 Feb 2020 at 00:38, Arpad Boda wrote: > > > > +1 (non-binding) > > Verified

Re: [DISCUSS] On HBase client retries (NIFI-6197)

2020-02-19 Thread Josh Elser
Thanks for sharing the code, Bryan! I lazily did not go digging. Looking into #onEnabled, we could change this to create its own Connection with a very low 1 or 2 retries with a very short retry duration. Throw that one away after we did our sanity check, set a high retry amount, and then

Re: [DISCUSS] On HBase client retries (NIFI-6197)

2020-02-19 Thread Bryan Bende
We do already expose the ability to configure the retries in the controller service [1], it was just a debate about what the default value should be. Currently it is set to 1 because we believed it was better to fail fast during the initial configuration of the service. A user can easily set it

[RESULT][VOTE] Release Apache NiFi 1.11.2

2020-02-19 Thread Joe Witt
Subj: [RESULT][VOTE] Release Apache NiFi 1.11.2 Apache NiFi Community, I am pleased to announce that the 1.11.2 release of Apache NiFi passes with 6 +1 (binding) votes 6 +1 (non-binding) votes 0 0 votes 0 -1 votes Thanks to all who helped make this release possible. Here is the

Re: Help with TLS with Client Auth

2020-02-19 Thread Pierre Villard
Hi Eduardo, I would first check that the ListenBeat is correctly exposing what you want using something like: openssl s_client -connect nifi-node: Thanks, Pierre Le mer. 19 févr. 2020 à 02:56, Eduardo Fontes a écrit : > Hi people! I'm using WindowsLogBeat (from Elastic Stack) to send Windows

Re: Execute SQL to MSFT SQLServer - getting error

2020-02-19 Thread Pierre Villard
Hi, Based on the error, it sounds like the driver you are using is not configured for integrated authentication. Can you share more details about how you configured your controller service? Thanks, Pierre Le mer. 19 févr. 2020 à 09:58, Samarendra Sahoo a écrit : > Dear all, > We are trying to

Jira contributor access

2020-02-19 Thread johan cronsioe
Hi, I would like Jira contributor access. My username is johancr. Regards, Johan

Execute SQL to MSFT SQLServer - getting error

2020-02-19 Thread Samarendra Sahoo
Dear all, We are trying to connect to SQLServer from Nifi installed on a RHEL Linux VM. We are not able to find a way to connect SQLServer configured with Integrated Security=*SSPI *with Windows login Authentication* ( Note : Kerberos not enabled ) *. We are trying to use *DBCPConnectionPool

Re: Jira contributor access

2020-02-19 Thread Aldrin Piri
Hi Johan, I've added you to the contributors list. Welcome to the community and we look forward to working with you! aldrin On Wed, Feb 19, 2020 at 12:07 PM johan cronsioe wrote: > Hi, > > I would like Jira contributor access. My username is johancr. > > Regards, > Johan >

Help with TLS with Client Auth

2020-02-19 Thread Eduardo Fontes
Hi people! I'm using WindowsLogBeat (from Elastic Stack) to send Windows events to NiFi (1.11.1) with processor ListenBeat (latest). My NiFi is a 3 node cluster under Linux with SSL. I'm trying to secure communication between Beat and NiFi using SSL/TLS with Client Auth. I created a