Hi Ara,
To follow up, I just opened a Jira [1] to remove that property entirely. It was
created in a legacy environment and isn’t a good solution anymore. The TLS
certificates should be properly configured (we can help with that if you need
it), but Trusted Hostname isn’t a secure behavior, as
With the NiFi TestRunner class for a Processor, is there a way to have it write
the output stream of the processor to disk so that it's not trying to store the
thing in a ByteArrayOutputStream? I've got a test case that uses a rather large
test file to verify some edge cases and I can't figure
Hello,
It looks like InvokeHttp creates an instance of the OkHttp client in
the onScheduled method which is called when the processor is started,
and when it creates the client it will specify a hostname verifier to
always accept whatever the trusted hostname is. So the issue is that
if trusted
Would it be possible to work around this by passing "upsert" as attribute
to flowfile? If so: where can i find some examples of using
PutDatabaseRecord with RecordReader to extract/save Json array?
Thank you
On Thu, Feb 7, 2019 at 1:03 PM Matt Burgess wrote:
> Yeah that's a gap that needs
In the InvokeHTTP processor, the Remote URL property supports Expression
Language but the Trusted Hostname does not. I can't use any form of stars,
*.*.my.expected.domain.com, and i cant use comma-separated values.
You can see this is a huge problem as domain name difference will cause
errors
(you can make it slightly less yucky by persisting the cache to shared
storage so you don't lose the contents when another node starts up,
but you do have to manually poke the clients)
On Tue, 12 Feb 2019 at 14:06, Bryan Bende wrote:
>
> As James pointed out, there are alternate implementations
As James pointed out, there are alternate implementations of the DMC
client that use external services that can be configured for high
availability, such as HBase or Redis.
When using the DMC client service, which is meant to work with the DMC
server, the server is a single point of failure. In a
We switched to HBase_1_1_2_ClientMapCacheService for precisely this
reason. It works great (we already had HBase which probably helped)
On Tue, 12 Feb 2019 at 12:51, Vos, Walter wrote:
>
> Hi,
>
> I'm on NiFi 1.5 and we're currently having an issue with one of the nodes in
> our three node
Hi,
I'm on NiFi 1.5 and we're currently having an issue with one of the nodes in
our three node cluster. No biggie, just disconnect it from the cluster and let
the other two nodes run things for a while, right? Unfortunately, some of our
flows are using a DistributedMapCacheService that have
