Github user michalklempa commented on the pull request:
https://github.com/apache/nifi/pull/257#issuecomment-200691342
@olegz there is http://snmpsim.sourceforge.net/ project, which can be used
for testing purposes. Some simulation files are available with distribution, so
basic testi
+1 (binding)
Ran through all build verification steps and all checks out. Local
testing as well as testing on single and cluster setup with security
including two-way SSL and LDAP interaction w/uname and pword on a
fairly high volume and complex flow checks out.
On Wed, Mar 23, 2016 at 5:46 PM,
Matthew Clarke wrote:
-- Forwarded message --
From: Paul Nahay
Date: Wed, Mar 23, 2016 at 10:31 AM
Subject: Your Distro
To: Matthew Clarke
This is the 2nd time I've gotten an email I sent to
dev@nifi.apache.org
returned to me:
Hi. This is the qmail-send program at apache.org.
Paul,
I strongly encourage you to consider the Apache Software Foundation's
Code of Conduct as you interact with this community [1].
[1] http://www.apache.org/foundation/policies/conduct.html
Thanks
Joe
On Wed, Mar 23, 2016 at 5:58 PM, Paul Nahay wrote:
> Wow. Thanks.
>
>
>
> This seems unnece
Wow. Thanks.
This seems unnecessarily complicated using the “Advanced” feature, given it’s a
standard boolean evaluation I’m trying to do. But I’m glad to hear there’s some
way to do it.
You know, assuming NiFi is written in Java (which I presume it is, if the
custom processors are as we
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 ma
Hello Apache NiFi Community,
I am pleased to be calling this vote for the source release of Apache NiFi,
nifi-0.6.0.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1079/
The Git tag is nifi-0.6.0-RC2
The Git c
Hope not to make copy/paste mistakes. I can share the code snippets, but
unfortunately not a trace. I didn't keep one and my efforts to restore
the broken code only leave me frustrated. (I've obliterated my NAR
several times, but the debugger tells me that the lines don't match up
when I step t
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/257#issuecomment-200559586
Pierre
You may want to rebase (merge conflicts) and push again since it's out of
sink.
Also, aside from unit tests would you mind giving some pointers on how to
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/285#issuecomment-200557606
Also, you may want to amend the commit message "Unepected" unless its a
new English word I haven't learned yet ;)
---
If your project is set up for it, you can reply to th
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/285#issuecomment-200557146
Ricky
Could you please take a look at
https://issues.apache.org/jira/browse/NIFI-1447 and see if it's what you are
looking for? If I remember correctly we don't rea
Russell
This doesn’t sound right. Would you care to share a code snippet on how you set
the attribute as well as stack trace?
Cheers
Oleg
> On Mar 23, 2016, at 5:33 PM, Russell Bateman
> wrote:
>
> I stumbled upon something peculiar in NiFi. I had been attaching an attribute
> to a flowfil
Russell
First, thank you for taking initiative!
Indeed we need to bring that JIRA to a closure. Having said that there is
actually a link in our Contributor Guide on interactive debugging
https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide#ContributorGuide-RunningNiFiinDebugmode
I stumbled upon something peculiar in NiFi. I had been attaching an
attribute to a flowfile in the session.read() call-back. The NiFi unit
testing framework tolerated this, but when I finally ran my processor
for real, it blew chunks (IllegalStateException). I solved the problem
by saving the n
I needed to break down and debug a processor I'm working on. I found a
JIRA issue a year old that's probably not been taken care of. I'd like
to help.
https://issues.apache.org/jira/browse/NIFI-513
I wrote this quickie on how to set up IntelliJ or Eclipse to accomplish
that. I'm using
Regarding the "undo" feature, just wanted to mention there is a ticket [1].
On a related note, there was also talk of confirmation dialogs as perhaps
an alternate way of catching unintended actions [2].
[1] https://issues.apache.org/jira/browse/NIFI-833
[2] https://issues.apache.org/jira/browse/NI
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/301
NIFI-483: Use ZooKeeper Leader Election to Auto-Elect Primary Node
NIFI-483: Use ZooKeeper Leader Election to Auto-Elect Primary Node
You can merge this pull request into a Git repository by running:
Paul,
Please create Jira tickets with your feature requests. I have not previously
encountered users making this request, so I want to ensure we capture all of
your desires for a successful implementation of this feature in order to
accurately estimate the resources necessary for it and priorit
Paul,
Have you tried joining the mailing list using the instructions here:
https://nifi.apache.org/mailing_lists.html
I know in the past, we have had issues with people who aren't
subscribed being unable to send to the list. This seems weird to me as
well, but since you are bringing up som
-- Forwarded message --
From: Paul Nahay
Date: Wed, Mar 23, 2016 at 10:31 AM
Subject: Your Distro
To: Matthew Clarke
This is the 2nd time I've gotten an email I sent to
dev@nifi.apache.org
returned to me:
Hi. This is the qmail-send program at apache.org.
I'm afraid I wasn't a
-- Forwarded message --
From: Paul Nahay
Date: Wed, Mar 23, 2016 at 10:51 AM
Subject: More Documentation Shortcomings
To: Matthew Clarke
Cc: dev@nifi.apache.org, Paul Nahay
>https://nifi.apache.org/docs.html#
This page lists special characters for attribute names, such that at
Github user markap14 closed the pull request at:
https://github.com/apache/nifi/pull/294
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Paul,
The expression you have above (
*${allAttributes('x','y'):isEmpty():not():or(${z:**isEmpty():not()})} * )
will not logically result in the same outcome as ( *
${allAttributes('x','y','z'):isEmpty():not(**)}*). I understand you
realize this, but I just want to clarify it for t
All,
It looks like the items that arose from testing have been resolved and
merged into master leaving just the release for this version. I will begin
the release process for RC2 based off of git
commit e4b7e47836edf47042973e604005058c28eed23b [1] [2]
[1]
https://git-wip-us.apache.org/repos/asf?
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/300
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/300#issuecomment-200414177
Okay, code looks good and I have played with this a bit confirming the
anticipated behavior for those processes that linger when stopping. +1 from me
and can merge into mas
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi/pull/300#discussion_r57181772
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java
---
@@ -1
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/295
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/300
NIFI-1676: Do not allow Processor to be started if state is STOPPING
Need to ensure that processor state is STOPPED, not STOPPING
You can merge this pull request into a Git repository by running:
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/294#issuecomment-200355764
@mcgilman I looked at the commit that you proposed. Looks good! +1. Thanks
for jumping in there and fixing that!
---
If your project is set up for it, you can reply to t
Thanks Matt,
Logs in Maven build are all OK (SUCCESS for each module at the end). I did
a new full build and I got a similar error (not exactly the same but
related to compilation). I tried once again and this is now OK. This is
really strange that Maven is not complaining about compilation issues
31 matches
Mail list logo
