Github user markap14 commented on the issue:

    https://github.com/apache/nifi/pull/2452
  
    @mattyb149 thanks for the update. This is definitely something that I think 
we should have added at the start. I'm curious about why the update to all of 
the reporting tasks, though. None of them make use of the name, as far as I can 
tell, so why both storing it off? Moreover, if we do want to store it off, then 
why not just have the setName() method have an @OnScheduled annotation and take 
in the ConfigurationContext. Then the abstract impl will automatically have the 
name set. It would not necessarily be available if being called from other 
@OnScheduled methods, but I think that's okay as long as it is documented - in 
such a case, you should call the method on the ReportingContext itself.


---

Reply via email to