Andre
BTW as a member of the PMC your votes are binding.
I am not quite sure the state of your snapshot version relative to the
release version. Definitely worth filing a JIRA and doing further
evaluation.
Thanks
Joe
On Fri, Nov 25, 2016 at 10:13 AM, Andre wrote:
> Joe,
Tony
I don't believe I ram contrib-check on Windows or Linux. I did that on osx.
My win environment is win10 home. Very recent Java 8 amd maven 3.3.9.
Thanks
Joe
On Nov 25, 2016 11:36 AM, "Tony Kurc" wrote:
> Joe Witt,
> I'm not able to build on Windows 10, I'm failing a
Joe,
-0 (non-binding)
When testing "rolling upgrade" I noticed that as nodes restarted they were
given new Node Ids (I suspect the NodeId is related to the version they
run?). This results on a cluster with 50% of nodes showing up as
disconnected.
Not sure if this is particular to my test
No problem. Thanks
On Nov 25, 2016 10:42 AM, "Andre" wrote:
Joe,
The non-binding was more in the sense it is not a show stopper (as I don't
foresee too many people upgrading that way) but I guess I should have made
it more explicit. :-)
Regarding SNAPSHOT, my bad...
Joe,
The non-binding was more in the sense it is not a show stopper (as I don't
foresee too many people upgrading that way) but I guess I should have made
it more explicit. :-)
Regarding SNAPSHOT, my bad... good news is that
nifi.build.revision=1b2b9f1
which happens to be Andy's last commit
Tony, Joe,
Sorry about the nifi-websocket-bundle Rat check issue, I should have
added apache-rat-plugin exclude configuration in its pom.xml like
other projects such as nifi-toolkit-tls does.
Created a JIRA for that:
https://issues.apache.org/jira/browse/NIFI-3103
I'll send a PR immediately. I
It's not a blocker for me, as it is clearly a config issue versus an actual
license issue
On Nov 25, 2016 4:18 PM, "Koji Kawamura" wrote:
> Tony, Joe,
>
> Sorry about the nifi-websocket-bundle Rat check issue, I should have
> added apache-rat-plugin exclude configuration
-1 (non-binding)
While verifying the LICENSE and NOTICE it occurred to me that some test data
that was included (by me sadly) in TestExtractHL7Attributes is MPL (category B)
licensed, which while ok for binary dependencies is not permitted for source
dependencies.
I'll PR and remove these
As we progress the extension registry concept we will provide for
versioned components which will also mean we can have multiple
versions of the same component on the same flow at the same time. In
this case we can do a pretty nice live loading of new capabilities
since it totally side steps the
Shweta,
While this may deviate from your initial requirements, NiFi offers the ability
to compress, resize, and extract metadata from your images. You can use NiFi
to build a image-processing pipeline for incoming images to prioritize and
route ~10% of images data that needs to arrive in 4
Joey - thanks for flagging that. That is indeed a no-go.
I've changed my vote to a -1 (binding) and as the RM I am cancelling this vote.
I'll get another RC together as soon as Joey's PR is available. It
will incorporate that as well as Koji's timeout adjustments for the
site-to-site-client
Thanks Koji. It would just end up getting excluded anyway from the
RAT check so that isn't a big deal. The point of RAT is to provide a
tool to help make enforcing licensing and proper notice. Ultimately,
we're responsible to do that regardless of RAT tells us (or doesn't
tell us).
Thanks for
All,
Still testing with the RC but this morning while searching for some API
details I noticed the case of duplicated nodes seems to have been
previously observed:
https://community.hortonworks.com/questions/59685/nifi-cluster-duplicate-nifi-node.html
On Sat, Nov 26, 2016 at 2:44 AM, Joe Witt
No, because of the class loading and general lack of Java hot swap capability,
to add or replace NAR files, the application must be restarted.
Is your prohibition on restarting the app due to the need for "100%" uptime or
a different reason? If you deploy a cluster, you can do a rolling update
Unless my back of the envelope math is way off, to transfer 50GB (400Gb) per
second, you would need 40 parallel 10GbE connections, assuming absolutely no
overhead. Your precision for "a few seconds" would need to be 40+ seconds using
a single 10 GbE link and optimal transmission speed.
From
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS
# Import keys file:
gpg --import KEYS
# [optional] Clear out local
sadly it might not stick. First pass generating the rc with it
failed. Not easy to tell if it is related so I'm trying again. If it
fails again i'll undo it and we'll just need to wait until we can get
on org.apache:apache:19. Not sure what their release ETA is.
The background on this is
+1 (binding).
Verified the primary finding from RC1 was addressed.
Verified the finding with RAT completion on windows from RC1 was addressed.
Verified the test timeout issue was improved.
Built using a full clean build with contrib check successfully on OSX,
Linux, and Windows 10.
Built using a
Hi Nifi Developers
Every time I want to add a custom processor to nifi, I need to restart nifi.
But in production I will not be allowed to restart Nifi. So is there a way to
install new nar files without restarting nifi.
/BR
Santosh
The information contained in this electronic message and any
19 matches
Mail list logo