The short answer is no, PutS3Object does not currently support a direct
equivalent of the AWS CLI's --no-verify-ssl option. There is an option to
provide your own SSLContextService, if you need to establish trust with
your proxy server (maybe, I'm not sure).
Hello, thanks everyone for the prompt response.
With your aid I was able to figure it out.
Mostly my problem was to understand the difference between the Grouping
Regular Expression and extracting the date parameter which in my case are
pretty much the same expression.
Also I have to admit that
Hi,
Bryan is correct, the idea here is to have the Ignite cache key (linked to
the content to retrieve from Ignite cache) based on an incoming flow file
attribute and that is why the processor requires an upstream connection. I
understand it might be confusing regarding the name of the processor
Hello,
I think the description of Cache Entry Identifier might be inaccurate
because it says ""A FlowFile attribute, or attribute expression used for
determining Ignite cache key for the Flow File content" but in the code it
does this:
String key =
Hello,
Sorry you are having problems with PublishMQTT. What MQTT broker are you trying
to hit? and could you pass along what configuration you have set (including
scheduling tab)? I'd like to try and reproduce if possible.
I'm guessing there is nothing more to that stacktrace? I ask (hoping that
Hi,
I have a workflow that compresses an file then invokes PutS3Object to store
in an S3 bucket. This processor works fine in a non-proxy environment,
where PutS3Object is parameterised correctly with the proxy settings, but
in a proxy environment I get the following error shown in the stack
