Re: Question bigqueryStreaming processor

Thanks Pierre for your help El jue., 13 de enero de 2022 3:12 p. m., Pierre Villard < pierre.villard...@gmail.com> escribió: > Hi Franco, > > I believe this post contains useful information: > >

Re: Question bigqueryStreaming processor

Thanks Pierre - you rock as always On Thu, Jan 13, 2022 at 1:12 PM Pierre Villard wrote: > > Hi Franco, > > I believe this post contains useful information: > https://stackoverflow.com/questions/43085896/update-or-delete-tables-with-streaming-buffer-in-bigquery > > In short: >> >> To check if

Re: Question bigqueryStreaming processor

Hi Franco, I believe this post contains useful information: https://stackoverflow.com/questions/43085896/update-or-delete-tables-with-streaming-buffer-in-bigquery In short: > To check if the table has a streaming buffer, check the tables.get response > for a section named streamingBuffer or,

Re: Question bigqueryStreaming processor

Thanks a lot Joe Nifi version 1.12.1 El jue, 13 ene 2022 a las 14:50, Joe Witt () escribió: > Franco > > I've pinged someone in the community who I suspect will know or be > able to quickly find out and reply back. But he is in France and it > is already later in the day so hang tight for a

Re: Question bigqueryStreaming processor

Franco I've pinged someone in the community who I suspect will know or be able to quickly find out and reply back. But he is in France and it is already later in the day so hang tight for a reply - hopefully tomorrow. Thanks On Thu, Jan 13, 2022 at 12:40 PM walter franco wrote: > > hello, > >

Re: question about the flow.xml.gz

Hi Nicholas, Unfortunately I can't see any great solutions here. It's a bit like asking 'if I give my house keys to this guy on the street, how do I stop them accessing my fridge?'. As a general rule, the Unix root user is the key to the castle. It is the user that must be protected at all costs,

Re: Processor SendTrapSNMP failed with error

Hi Anton, I opened a NiFi Jira ticket for the problem, which you may watch for updates. The problem appears to be code-related, since the Net-SNMP tool works on the local subnet but the SNMP processors do not. Best Regards, Lehel Boér

RE: Running NiFi with uncompressed flow.xml?

Hello Can be the flow.xml.gz protected by a password (managed by NiFi) ? This could prevent this file to be read by unauthorized users ( like root) Regards. N. -Original Message- From: Bryan Bende Sent: Thursday, January 13, 2022 5:37 PM To: users@nifi.apache.org Subject: Re:

Re: Running NiFi with uncompressed flow.xml?

To add to Joe's point, the flow.xml.gz should be treated like an internal component of NiFi that you don't really even know is there. It is not a public API and is free to be changed by developers, and it is also not portable across environments unless you are using the same sensitive property key

Re: ConsumeJMS causing multiple BIND/UNBIND request

Probabl you faced https://issues.apache.org/jira/browse/NIFI-7563. Check a newer version. On Thu, 13 Jan 2022 at 13:02, Joe Witt wrote: > Solace is a commonly used JMS provider with NIFi and it is very likely > such an issue has been addressed. Please test/attempt this on a newer > version of

Re: Running NiFi with uncompressed flow.xml?

Hello, Joe Witt wrote: /At this time there is not./ OK, thanks for the clear answer. /The better answer from a version management point of view is usage of the Flow Registry and versioned flows./ But then it would be residing in a different system (the registry), as far as

Re: Running NiFi with uncompressed flow.xml?

Troels, At this time there is not. The flow.xml.gz file isn't meant for external usage generally and it might as well be called 'nifivoodoofiledontmesswiththis.custom' The better answer from a version management point of view is usage of the Flow Registry and versioned flows. NiFi isn't

Running NiFi with uncompressed flow.xml?

Hello, Is it possible to have NiFi running in a state where it uses an uncompressed flow.xml file? - I.e. where it does not use a compressed flow.xml.gz file? (The flow.xml files that I've seen have not been huge, so I don't quite understand why it's compressed in the first place.) This is

Re: ConsumeJMS causing multiple BIND/UNBIND request

Solace is a commonly used JMS provider with NIFi and it is very likely such an issue has been addressed. Please test/attempt this on a newer version of NiFi. Fixed related to JMS since 1.11

Re: ConsumeJMS causing multiple BIND/UNBIND request

NiFi 1.11 .0 On Thu, 13 Jan 2022 at 18:27, Juan Pablo Gardella < gardellajuanpa...@gmail.com> wrote: > Which Nifi version are you using? > > On Thu, 13 Jan 2022 at 09:14, nayan sharma > wrote: > >> Hi All, >> >> >> >> We are using consumeJMS to consume messages from the Solaxce system from >>

Re: ConsumeJMS causing multiple BIND/UNBIND request

Which Nifi version are you using? On Thu, 13 Jan 2022 at 09:14, nayan sharma wrote: > Hi All, > > > > We are using consumeJMS to consume messages from the Solaxce system from > multiple queues but we are getting multiple bind/unbind requests. > > As we are getting alerts

ConsumeJMS causing multiple BIND/UNBIND request

Hi All, We are using consumeJMS to consume messages from the Solaxce system from multiple queues but we are getting multiple bind/unbind requests. As we are getting alerts *SYSTEM_LOGGING_LOST_EVENT* alerts on solace production appliance leading to buffer pool is exhausted. We have seen