a MockComponentLog:
https://github.com/apache/nifi/blob/master/nifi-mock/src/main/java/org/apache/nifi/util/MockComponentLog.java.
From that you can get your messages and check if you logged the
specific one(s) you care about.
Regards,
Matt
On Thu, Aug 25, 2016 at 1:22 PM, Russell Bateman
<russell.b
escaping into the wild.
Regards,
Matt
On Thu, Aug 25, 2016 at 12:51 PM, Russell Bateman
<russell.bate...@perfectsearchcorp.com> wrote:
From my custom processor, I'm throwing a ProcessException that never reaches
my catch in the JUnit test. I already have several other JUnit tests w
w a before, after, and provide some text about the
changes you'd like?
Your screenshot looks great to me but it also isn't obvious what changed.
On Fri, Aug 19, 2016 at 7:49 AM, Russell Bateman
<russell.bate...@perfectsearchcorp.com> wrote:
As a consumer of NiFi and a developer of proprietar
As a consumer of NiFi and a developer of proprietary processors I'm a
little concerned by what I see here too. In fact, I'd like to read some
document supporting/justifying the UI changes, which is not to say that I
presume to condemn them, just that I'd like to understand the reasoning.
The
e API's in action.
> The UI uses these API's exclusively.
>
> Also the API's have been completely refactored in the upcoming 1.0.0
> release to align with the authorization policies of each resource. So the
> answers to your questions will depend on which version your running.
>
> Ma
use-to-test-your-public-rest-api
> [2] http://commandlinefanatic.com/cgi-bin/showarticle.cgi?article=art034
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7
s these API's exclusively.
>
> Also the API's have been completely refactored in the upcoming 1.0.0
> release to align with the authorization policies of each resource. So the
> answers to your questions will depend on which version your running.
>
> Matt
>
> Sent from
Ah, for (9), I used system-diagnostics. (I had not spelled it correctly
when trying it before.)
On Fri, Jul 8, 2016 at 3:35 PM, Russell Bateman <
russell.bate...@perfectsearchcorp.com> wrote:
> I'm trying to figure out how to use the ReST (nifi-api) interface to
> accomplish a numb
I'm trying to figure out how to use the ReST (nifi-api) interface to
accomplish a number of things. First, I've played successfully with it
doing simple things like getting configuration, a list of existing
processors, and the like. I've even discovered that in
enarios which explain to the user proper handling.
> You can also use the PropertyDescriptor of each property to explain
> its intended relationship to other properties.
>
> Does that seem like it will take care of your case?
>
> Thanks
> Joe
>
> On Thu, May 12,
, May 12, 2016 at 1:25 PM, Russell Bateman
<russell.bate...@perfectsearchcorp.com> wrote:
How are folk specifying processor properties in the case where one of two
properties is required, but not both? I'm just wondering if there's a best
practice here or must I say something in the descr
How are folk specifying processor properties in the case where one of
two properties is required, but not both? I'm just wondering if there's
a best practice here or must I say something in the description?
For example, I've written a processor that implements Apache Velocity
templating. I
/controller services/reporting tasks to use them. We
should also create a ticket to update the developer documentation to
describe the annotations usage.
[1] http://docs.oracle.com/javase/tutorial/java/annotations/repeating.html
Dan
On Tue, Apr 19, 2016 at 7:23 AM Russell Bateman <
russell.b
On Friday, April 15, 2016 7:46 PM, Russell Bateman
<russell.bate...@perfectsearchcorp.com> wrote:
What's the syntax for defining more than one dynamic property for a
processor? I need to specify up to three distinctly different ones and
attempting to do it all in
@DynamicProperty(
What's the syntax for defining more than one dynamic property for a
processor? I need to specify up to three distinctly different ones and
attempting to do it all in
@DynamicProperty(
name = "{blah,blah2,blah3}",
value = "{\"blah-value\",\"blah2-value\",\"blah3-value\"}",
Welcome Idioma...
1) You'll want to subsume your new processors under deeper Java packages
(you probably knew that).
2) In addition to the Java code, you'll add:
-src
-main
- resources
- META-INF
- services
- org.apache.nifi.processor.Processor
containing a list
Oleg,
Agreed. As I started only a few months ago, I have been using
AtomicReference and it has been reliable and satisfied all my needs.
(Just sayin'.)
Best
On 04/14/2016 05:22 AM, Oleg Zhurakousky wrote:
A bit unrelated, but how do you guys feel if we deprecate ObjectHolder so it
could
r( flowfile, new
ProcessorRelationships().getSuccess() );
}
On 03/23/2016 03:42 PM, Oleg Zhurakousky wrote:
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 Bate
Uwe,
When I asked this question a few days ago. What you're doing is rolling
your whole processor into a NAR instead of JARing it first, then rolling
the JAR into a NAR. This doesn't work and still won't work when they fix
it (not just for the reason of /additional//Details.html/ because
Uwe,
While my usage is surely unrelated to yours, I do exactly this thing
which is to process a CSV producing as many new output flowfiles as
there are lines and the names of these flowfiles are, in my case,
conveniently chosen based on the significant content of each line (so no
problem
201 - 220 of 220 matches
Mail list logo
