[jira] [Updated] (NIFI-3109) Refactor TimerDrivenSchedulingAgent
[ https://issues.apache.org/jira/browse/NIFI-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-3109: -- Fix Version/s: (was: 1.2.0) > Refactor TimerDrivenSchedulingAgent > --- > > Key: NIFI-3109 > URL: https://issues.apache.org/jira/browse/NIFI-3109 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Minor > > While working on determining reasons for bug described in NIFI-2886, I've > noticed an opportunity for some refactoring which in a way is significant as > it greatly reduces the code base, eliminates unnecessary synchronization as > well as provides for better reusability of object instances. (i.e., Currently > for each task an instance of ContinuallyRunProcessorTask is created while the > same instance could be reused for all tasks, and more) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3109) Refactor TimerDrivenSchedulingAgent
[ https://issues.apache.org/jira/browse/NIFI-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-3109: --- Status: Patch Available (was: Open) > Refactor TimerDrivenSchedulingAgent > --- > > Key: NIFI-3109 > URL: https://issues.apache.org/jira/browse/NIFI-3109 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.2.0 > > > While working on determining reasons for bug described in NIFI-2886, I've > noticed an opportunity for some refactoring which in a way is significant as > it greatly reduces the code base, eliminates unnecessary synchronization as > well as provides for better reusability of object instances. (i.e., Currently > for each task an instance of ContinuallyRunProcessorTask is created while the > same instance could be reused for all tasks, and more) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-3109) Refactor TimerDrivenSchedulingAgent
[ https://issues.apache.org/jira/browse/NIFI-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-3109: --- Description: While working on determining reasons for bug described in NIFI-2886, I've noticed an opportunity for some refactoring which in a way is significant as it greatly reduces the code base, eliminates unnecessary synchronization as well as provides for better reusability of object instances. (i.e., Currently for each task an instance of ContinuallyRunProcessorTask is created while the same instance could be reused for all tasks, and more) (was: While working on determining reasons for bug described in NIFI-2886, I've noticed an opportunity for some refactoring opportunity which in a way is significant as it greatly reduces the code base, eliminates unnecessary synchronization as well as provides for better reusability of object instances. (i.e., Currently for each task an instance of ContinuallyRunProcessorTask is created while the same instance could be reused for all tasks, and more)) > Refactor TimerDrivenSchedulingAgent > --- > > Key: NIFI-3109 > URL: https://issues.apache.org/jira/browse/NIFI-3109 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Oleg Zhurakousky >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.2.0 > > > While working on determining reasons for bug described in NIFI-2886, I've > noticed an opportunity for some refactoring which in a way is significant as > it greatly reduces the code base, eliminates unnecessary synchronization as > well as provides for better reusability of object instances. (i.e., Currently > for each task an instance of ContinuallyRunProcessorTask is created while the > same instance could be reused for all tasks, and more) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
