Member since
02-15-2017
12
Posts
1
Kudos Received
0
Solutions
06-23-2017
07:14 PM
Thanks Shashank, logs are now rolling over on both time and size triggers. Awesome!
... View more
06-23-2017
12:48 AM
1 Kudo
I have NiFi 1.2.0 installed on the Windows 2012 R2 server, it creates the standard logs files as under:
nifi-bootstrap.log nifi-app.log nifi-user.log Issue is that these files are not rolling over daily or based on size. Can someone help? I have attached the logback.xml file. Also, are the changes to this logback.xml dynamically implemented, or it requires NiFi to get into effect?
... View more
Labels:
- Labels:
-
Apache NiFi
06-20-2017
12:13 AM
Matt, how would the properties set in custom properties file be accessed within the custom controller service's onConfigured method? Thanks.
... View more
03-01-2017
05:16 PM
Your explanation helped me in identify the core issue. You are correct in assuming I was calling the service implementation rather than the interface. Once I made appropriate changes in my code and unit tested, I was able to drop in NiFi and have the integration testing done. I was able to configure the custom service by adding it in drop down on the custom Lookup processor in NiFi Web UI. THANK YOU for all the help!!!!
... View more
02-28-2017
10:48 PM
I have built a custom controller service and custom processor. I am able to build and run tests in IntelliJ on my laptop. Once the maven build is successfully complete, I copied all the 3 nar files and dropped them in the lib folder of NiFi. In NiFi web interface, I can the see my custom service in Controller Service page. I am able to configure it and enable it. NiFi logs confirms the service is online. Now, when I drop the custom processor, I cannot see the service to choose in drop down. Event though it is service is running. I verified the dependencies in pom for all nar modules.
nifi-customservice-api-nar nifi-customservice-nar nifi-LookupProcessor-nar Following is the error in the NiFi app log: java.lang.IllegalArgumentException: ControllerServices may be referenced only via their interfaces; class org.pwc.nifi.customservice.LookupService is not an interface
at org.apache.nifi.attribute.expression.language.StandardPropertyValue.asControllerService(StandardPropertyValue.java:172) ~[nifi-expression-language-1.1.1.jar:1.1.1]
at org.pwc.nifi.customservice.LookupProcessor.onTrigger(LookupProcessor.java:79) ~[na:na]
at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) ~[nifi-api-1.1.1.jar:1.1.1]
at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099) ~[nifi-framework-core-1.1.1.jar:1.1.1]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-1.1.1.jar:1.1.1]
at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-1.1.1.jar:1.1.1]
at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132) [nifi-framework-core-1.1.1.jar:1.1.1]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [na:1.8.0_91]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) [na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_91]
at java.lang.Thread.run(Unknown Source) [na:1.8.0_91] I would appreciate if someone can help with :
Resolving missing service in drop down when configuring the processor in properties. Resolving error "java.lang.IllegalArgumentException: ControllerServices may be referenced only via their interfaces" Thank you.
... View more
Labels:
- Labels:
-
Apache NiFi
02-15-2017
11:44 PM
Koji Kawamura,
Did you get chance to work on the offset reset feature? Having ability to reset offset to a target value is necessary in case the pipeline needs to be reprocessed.
... View more