Apache NiFi Community,
The https://nifi.apache.org/security.html page has been updated with 3
vulnerabilities discovered in previous NiFi versions which have been
resolved in release 1.10.0. The severity of these were determined to be two
'low' and one 'medium'. Dependency vulnerabilities that
Hi Mike,
In the 1.10 release the EasyRules Controller service has documentation
related to how rules can be defined and how the service can be configured.
Also I am working on a blog post detailing the Rules API in general and how
it can be leveraged using InvokeScriptedProcessor. Hopefully this
https://issues.apache.org/jira/browse/NIFI-6885
On Tue, Nov 19, 2019 at 9:57 AM Joe Ferner wrote:
> I'm filing a JIRA for the logUnbuildableDestination logging bug and will
> knock this out shortly.
>
> Looking deeper on your warning, it sounds like your Flow File has a
> jms_destination
I'm filing a JIRA for the logUnbuildableDestination logging bug and will
knock this out shortly.
Looking deeper on your warning, it sounds like your Flow File has a
jms_destination attribute on it which is separate than then PublishJMS
processor Destination Name property. While the Destination
Hi Si,
Thanks for jumping in. I am not aware of any existing work on such a
processor, but it'd definitely be a nice addition. Feel free to open a pull
request with your processors when you feel it's ready for a review. IMHO,
you can open a pull request for a Put processor without the List/Fetch
There are two methods in AtomicDistributedMapCache, one is fetch which
returns an AtomicCacheEntry which has , the second is replace
which takes an updated entry and will replace if the revision in the
updated entry matches the revision stored in the cache (i.e. no one
else has updated it).
In
Where does the value from revision come from on the call to replace in
AtomicDistributedMapCacheClient? What should it be set to on a call to replace
if a revision isn’t provided? I’m looking at the WaitNotifyProtocol class and
it looks like revision isn’t even used. If that’s the case then the
Well, here is the first version:
https://github.com/si-sun/nifi-smb-processors
It supports normal username / password authentication, missing dir
creation, conflict resolution and share access setting.
Regards
Si
Am Do., 14. Nov. 2019 um 19:20 Uhr schrieb Si :
> Hello
>
> We're using NiFi on
Are there any docs yet on the rules engine-related changes that have been
added?
Thanks,
Mike
