Joe,
Primarily, I believe the use case is legacy flows pre-dating the existence
of "delete attribute" functionality. The most "correct" solution may be to
delete the attribute, but that doesn't mean we should break backwards
compatibility.
Brandon
On Fri, Jan 19, 2018 at 5:33 PM Joe Percivall
+1 - binding - release this package as minifi-0.4.0
Ran through the release helper guide and LGTM, thanks for taking care of
the RM Aldrin!
Pierre
2018-01-19 22:31 GMT+01:00 Marc Parisi :
> +1 binding to release this package as minifi-0.4.0
>
> * Verified sigs/hashes
>
Hey Mark,
Yeah, at the time I couldn't think of a use-case that a user would want to
set an attribute to empty so when I added the validator for the stateful
portion, I added the empty validator as well. That said, I don't see a need
to keep it if it's preventing your use-case. Curious, what is
+1 binding to release this package as minifi-0.4.0
* Verified sigs/hashes
* Built and ran with typical test flows across builds ( to include
SiteToSite )
Looks good thanks!
On Fri, Jan 19, 2018 at 3:28 PM, Bryan Bende wrote:
> +1 binding
>
> Ran through everything in
+1 binding
Ran through everything in the release helper and looked good, thanks!
On Fri, Jan 19, 2018 at 3:03 PM, Matt Gilman wrote:
> +1 Release this package as minifi-0.4.0
>
> Verified hashes, signature, build, etc. Ran sample flows and everything
> looks good.
>
>
sweet!
On Fri, Jan 19, 2018 at 2:46 PM Michael Moser wrote:
> Somebody's Jenkins is spamming everyone who has made a commit recently!
>
>
> -- Forwarded message --
> From:
> Date: Fri, Jan 19, 2018 at 11:23 AM
> Subject:
Hi Mark,
After reading the JIRA [1] and the PR for the UpdateAttribute
modifications, I believe this was simply an unintended consequence of the
code changes. If you would like to write a new JIRA, then I'm sure we can
restore the "Set Empty String" functionality when not storing attributes in
I'd also vote for an OSGi backend (in the long term). It's something that
has been on my mind (and mentioned) for years now.
The Nar classloader ecosystem is trying to implement features of OSGi (and
doing it somewhat poorly at that, if you are honest). Not saying that OSGi
is the right
Hello,
I'm try to parse CEF using ParseCef processor.
It working normal when I generate flow file using custom text in CEF format.
But when I send same text to ListenUDP processor and forward it to ParseCef
processor, ParseCef processor returns "enexpected Exception string index out
of range: -5
Hi Andy,
I submitted a ticket to document our need.
Here is the link - https://issues.apache.org/jira/browse/NIFI-4797
Regards,
Virgil
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
Hi guys, one of my colleagues was working on a remote deploy tool trying to
start NiFi remotely on a windows system(NiFi package is on the windows
system).
I don't know how exactly the deployment tool works, but the basic flow is
to launch Ansible locally which uses winrm to remotely
launch NiFi
11 matches
Mail list logo