Re: get controller service's configuration

You can get the current property values of a controller service from the processor by using the ProcessContext object. For example, in GetHTTP [1], in the @OnScheduled method, you could do: context.getControllerServiceLookup().getControllerService("my-controller-service-id”);

Re: get controller service's configuration

Thanks Koji, I checked the link you provided and I think getting a DataSource is no different than getting the DBCP service(they could just get the connection). Actually I was trying to get the configured driver class to check the database type. Regards, Ben 2017-08-10 9:29 GMT+08:00 Koji

Re: NiFi RecordPath Question

Hi David, This is absolutely the correct place to ask these questions. There is also a mailing list more focused on the user experience and less of the development discussion at us...@nifi.apache.org which may help as well. Mark Payne contributed most of the record processing code, and has

Re: get controller service's configuration

Hi Ben, I'm not aware of ways to obtain configurations of a controller from a processor. Those should be encapsulated inside a controller service. If you'd like to create DataSource instance instead of just obtaining a connection, this discussion might be helpful:

get controller service's configuration

Hi guys, I have a customized processor with a DBCP controller service as a property. I could get the DBCP controller service in my code, but does anyone know how to obtain all the configurations of the DBCP controller service in java code(e.g. Database Connection URL, Database Driver Location,

NiFi RecordPath Question

https://nifi.apache.org/docs/nifi-docs/html/record-path-guide.html#filters Apologies in advance - I'm sure this email alias isn't used for questions, but I did see it at the top of the page in the link above. Is it possible to do any AND condition with using record path? Given the below json

Re: MINIFI-350 minifi-cpp end-to-end integration testing framework

MiNiFi cpp team, I have created the initial pytest/docker based test framework as well as a few initial test cases. Please review & merge the PR (https://github.com/apache/nifi-minifi-cpp/pull/126) at your convenience. Regards, Andy I.C. From:

Re: MINIFI-350 CMake target for docker integration tests

Yeah, my vote would definitely be to have the separate targets. I like having a lot of options for testing but definitely like being able to minimize needed dependencies appropriate to desired level of evaluation. In terms of naming, would likely avoid calling these integration given their

Re: FlowFile Logging

ah that sounds perfect for what I need to do. Thank you! On Tue, Aug 8, 2017 at 7:20 PM, Andy LoPresto wrote: > You can add an appender in the conf/logback.xml file which handles > “org.apache.nifi” and anything of ERROR level and writes to a separate log > file, which you

Re: MINIFI-350 CMake target for docker integration tests

These are good points. Having a separate target makes sense, plus it'll reduce risk of interfering with the existing native development workflow. What shall we call the new target? Some possibilities: - make sip (system integration tests) - make docker-verify - make verify-docker - make

Re: MINIFI-350 CMake target for docker integration tests

Andy, This is great stuff. To facilitate use by developers we should probably come to agreement on terminology. In my opinion, it seems that you are facilitating more system integration testing (SIT) based on our discussions. While what you are doing doesn't preclude you from integrating one or

RE: [EXT] Re: Updating users through Rest API

Matt, Sorry I forgot to update the community on this. I tried what you suggested and it worked like magic. So the right way to do it is 1. Create a user first and get his UID, do not give him a UID and give Version: 0 (POST) 2. Get a UserGroup (json format). (GET) 3. Add the new user using

MINIFI-350 CMake target for docker integration tests

MiNiFi cpp team, I am currently working on MINIFI-350. I have an integration test framework plus a few integration tests which are invoked via a new script called docker/DockerVerify.sh (https://github.com/achristianson/nifi-minifi-cpp/blob/MINIFI-350/docker/DockerVerify.sh?). This is

MINIFI-368 exclude hidden files when scanning for src files

MiNiFi cpp team, I have submitted a PR which fixes an issue where having a file open in vim causes the cmake build to fail. It fails because the BuildTests.cmake file includes hidden files in its scan for source files. Please have a look at https://github.com/apache/nifi-minifi-cpp/pull/125?

Date format method in NiFi Expression Language doesn't support negative timestamp

Hello，Everyone Now i found the date format method in NiFi Expression Language doesn't support negative timestamp which means the time before 1970.01.01 . Is there any idea on how to achieve this, and can I define my own NiFi Expression Language. Thanks for your early reply. Best