Re: Whitelisting Proxy Host values in a Container Environment?

No, ignoring the port could lead to the same malicious host injection in the scenario where multiple services are hosted on the same machine (i.e. nifi-1 at nifi.apache.org:8443 and nifi-2 at nifi.apache.org:8444). Is the port for each different than what is set

Re: [EXT] ReplaceText cannot consume messages if Regex does not match

Exactly, I know it is not an issue in the replace text code, but it happens inside it. If we are using the ReplaceText in multiple places, it increases the flow design complexity. We need to evaluate all expressions before sending to the processor, to be sure will not fail in ReplaceText

RE: [EXT] ReplaceText cannot consume messages if Regex does not match

I understand the issue now, I’m not sure that a failure of ReplaceText is the best place to catch this though. The reason I’m not sure it’s the best place is what happens if there are multiple failures because you had multiple expressions, just having them all routed to the same failure

Re: [EXT] ReplaceText cannot consume messages if Regex does not match

Is the actualSettlementDate attribute's value in the "MM/dd/" format, with no other text in front of the date? For instance, "10/18/2018 12:30:00" is parsable by the "MM/dd/" format, but "12:30:00 10/18/2018" is not. On Thu, Oct 18, 2018 at 12:02 PM Juan Pablo Gardella <

Re: question about ConsumeKafka metrics for incoming data

> The value should be close to how many bytes have been consumed from Kafka. Very good hint. Thanks Jeff. And thanks Bryan too ! Dominique Le jeu. 18 oct. 2018 à 17:52, Jeff a écrit : > Dominique, > > The "bytes in" value represents how many bytes have been received from an > incoming

Re: [EXT] ReplaceText cannot consume messages if Regex does not match

At *search value*:(?s)(^.*$) At *Replacement value*: *${actualSettlementDate:toDate('MM/dd/'):format("-MM-dd'T'00:00:00.000")}* The actualSettlementDate is a flowfile attribute. The problem is the replacement value is evaluated inside the processor and the *toDate *method fails.

Re: question about ConsumeKafka metrics for incoming data

Dominique, The "bytes in" value represents how many bytes have been received from an incoming connection. Since ConsumeKafka is directly consuming data from Kafka (a "source" processor), and not from a connection from an upstream processor, it won't show a value for "bytes in". If you want to

Re: question about ConsumeKafka metrics for incoming data

Hello, Bytes in is the # of bytes read from incoming flow files. Since source processors don't have incoming flow files they will never have bytes in or flow files in. -Bryan On Thu, Oct 18, 2018 at 11:25 AM Dominique De Vito wrote: > > Hi, > > While running a ConsumeKafka processor, I noticed

Who uses NiFi Cluster in Docker ?

Hi, I'm looking for experiences and return on experience in running a Nifi Cluster in production using docker/kubernetes/mesos. Is it working well ? Is it stable ? Does it handle well a high workload ? Thanks for you feedbacks, Guillaume.

RE: [EXT] ReplaceText cannot consume messages if Regex does not match

What processor are you defining your expression in? I also may be misunderstanding the problem because I don’t see any regular expressions anywhere. Can you create a sample workflow showing your issue so I can take a look at it. Thanks Shawn Weeks From: Juan Pablo Gardella Sent: Thursday,

Re: [EXT] ReplaceText cannot consume messages if Regex does not match

No, it's not a valid date. I would like if it an error happens, I would like to throw the flowfile to failure and continue. On Thu, 18 Oct 2018 at 12:19 Shawn Weeks wrote: > Any expression language syntax has to be correct or the processor won’t > run. I’m not sure there is any way to work

question about ConsumeKafka metrics for incoming data

Hi, While running a ConsumeKafka processor, I noticed there are metrics for incoming data, but there was no value (like "bytes in") provided in the UI. And as far as I have digged into the ConsumeKafka processor, I didn't found any code related to feeding the metrics related to the incoming

RE: [EXT] ReplaceText cannot consume messages if Regex does not match

Any expression language syntax has to be correct or the processor won’t run. I’m not sure there is any way to work around that except to explicitly check that the value you are trying to evaluate is valid. Is the attribute “tradeDate” coming from the contents of a flow file or is it defined

Re: Whitelisting Proxy Host values in a Container Environment?

Thanks Andy. Would a solution involving only checking the hostname and not the port be considered? That's where our heartache is coming from. The documentation hints that this is supported by referencing the format host[:port] but the port is not currently optional (unless using 80/443 I suppose).

RE: [EXT] ReplaceText cannot consume messages if Regex does not match

Hi Juan, What version of NiFi are you running on? What mode are you running ReplaceText in, all text or line by line? Other settings that might be important? What’s your RegEx look like (if your able to share). --Peter From: Juan Pablo Gardella [mailto:gardellajuanpa...@gmail.com] Sent:

ReplaceText cannot consume messages if Regex does not match

Hi all, I'm seeing that ReplaceText is not able to consume messages that does not match regex. It keeps all the messages in the input queue instead of sending them to failure relationship. Is this the intended behavior or I have to file a ticket in order to be fixed? In that way, the processor is

Re: Whitelisting Proxy Host values in a Container Environment?

Jon, Sorry to hear that securing NiFi is proving difficult for you. The reason this feature was introduced is because prior to this check being enforced, a malicious Host header in requests could poison the server and return untrusted resources. Please see the Admin Guide [1] section on Proxy