Github user pvillard31 commented on the issue:

    https://github.com/apache/nifi/pull/379
  
    Thanks for the review @apiri!
    I still need to take into account some of your comments but I rebased the 
PR against master. While doing some additional testing, for a reason I can't 
explain yet, I was unable to use the ListProcessor:
    
    ````
    2016-06-21 23:28:56,127 WARN [Timer-Driven Process Thread-9] 
o.a.n.c.t.ContinuallyRunProcessorTask Administratively Yielding 
ListAlluxio[id=42835c14-3896-47e0-95ae-ce8266e7c030] due to uncaught Exception: 
java.lang.NullPointerException: Name is null
    2016-06-21 23:28:56,130 WARN [Timer-Driven Process Thread-9] 
o.a.n.c.t.ContinuallyRunProcessorTask 
    java.lang.NullPointerException: Name is null
        at java.lang.Enum.valueOf(Enum.java:236) ~[na:1.8.0_77]
        at 
alluxio.exception.AlluxioExceptionType.valueOf(AlluxioExceptionType.java:19) 
~[na:na]
        at alluxio.exception.AlluxioException.from(AlluxioException.java:69) 
~[na:na]
        at alluxio.AbstractClient.retryRPC(AbstractClient.java:324) ~[na:na]
        at 
alluxio.client.file.FileSystemMasterClient.listStatus(FileSystemMasterClient.java:271)
 ~[na:na]
        at 
alluxio.client.file.BaseFileSystem.listStatus(BaseFileSystem.java:188) ~[na:na]
        at 
alluxio.client.file.BaseFileSystem.listStatus(BaseFileSystem.java:179) ~[na:na]
        at 
org.apache.nifi.processors.alluxio.ListAlluxio.onTrigger(ListAlluxio.java:91) 
~[na:na]
        at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 ~[nifi-api-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
        at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1077)
 ~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
        at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_77]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_77]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_77]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_77]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_77]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_77]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
    ````
    
    I'll try to dig more into this tomorrow. Otherwise, a guy from Alluxio 
reached me to propose his help if needed on this PR, I guess I can ask him to 
have a look and make some comments.


---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to