Testing processor logging message in Junit tests

Hi Does anyone know how to test for logging messages generated by my processors in my Juint tests for that processor?I am trying to determine whilst testing my processor if I have entered an exception, where I would just normally log a warning or an Error but necessarily end up on the failure

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Hi: I have started working on implementing a controller for creating creds provider and changing the createClient method to use the controller.    If there is any advice/feedback on this, please let me know. Thanks again. Mans On Friday, January 8, 2016 12:48 PM, M Singh

Re: about the debug of nifi

Did you go through the last step in the README of identifying ‘main’? There are no sources since what you are running is ‘org.apache.nifi.NiFi’. Cheers Oleg On Jan 5, 2016, at 1:51 AM, 522250...@qq.com wrote: i want to debug nifi ,and i find the guidence in wiki.Then

Re: Testing processor logging message in Junit tests

This sounds like something I’m about to come up against so I’ve raised NIFI-1376 for it and pushed up a possible fix that allows TestRunner to return a list of logged messages for each level (e.g. info, warn etc). TestRunner also provides access to any Controller Service log messages if

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Mans You are right that it is confusing and breaking would be cleaner. So let's be sure to annotate this and as we fork to begin 1.x line we can clean all such things up and remove the extraneous code and properties. We will use the yetus api markings to make these areas clearly not allowed for

Re: Groovy unit tests

Big +1 Sent from my iPhone On Jan 4, 2016, at 18:30, Andy LoPresto > wrote: I am considering writing unit tests in for new development/regression testing in Groovy. There are numerous advantages to this [1][2] (such as map

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Mans, Sounds great. Feel free to let us know if you have any issues and we are happy to work through it with you. Thanks again for taking this work on! On Sat, Jan 9, 2016 at 4:21 PM, M Singh wrote: > Sounds like a plan, Aldrin. Let me explore this path. >

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

+1 on converting AbstractAWSProcessor to using AWSCredentialsProvider, and +1 to adding a controller service for AWS creds. I would like to help. The current AbstractAWSProcessor.onScheduled method already contains code to probe for the REGION PropertyDescriptor and modify the AWS client based

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Sounds like a plan, Aldrin.   Let me explore this path. Mans On Saturday, January 9, 2016 1:16 PM, Aldrin Piri wrote: Mans, In the way I specified via the linked snippet, we could potentially just have it implement the AWSCredentialsProvider signature, and in the

Re: Testing processor logging message in Junit tests

Are you looking for something similar to this: http://stackoverflow.com/questions/1827677/how-to-do-a-junit-assert-on-a-message-in-a-logger Sent from my iPhone On Jan 9, 2016, at 09:06, DAVID SMITH > wrote: Hi Does anyone know how to

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Hi Aldrin: Even if we subclass AbstractAWSProcessor and overwrite the onScheduled method, we still have to add (rather then replace createClient with aws creds argument) a createClient method that would take the credential provider argument rather than the aws credentials argument (the current

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

Mans, I think the ControllerService is definitely the right play moving forward. What I think we can do is subclass the current AWSAbstractProcessor and override onScheduled to provide a way to interact with the ControllerService and, should one not be configured, defer to the parent

[DISCUSS] Proposal for an Apache NiFi sub project - MiNiFi

NiFi Community, I'd like to initiate discussion around a proposal to create our first sub-project of NiFi. A possible name for it is "MiNiFi" a sort of play on Mini-NiFi. The idea is to provide a complementary data collection agent to NiFi's current approach of dataflow management. As noted in

Re: [DISCUSS] Proposal for an Apache NiFi sub project - MiNiFi

Some thoughts - so on the roadmap Joe posted a couple days ago, HA was a big focus (in 1.X). NiFi becomes a bigger better "hub", but likely those capabilities don't scale down quite as well. Thanks for kicking off this discussion, Joe, I think now is the time think about what we need to do about