[ 
https://issues.apache.org/jira/browse/FLUME-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474409#comment-13474409
 ] 

Brock Noland edited comment on FLUME-1630 at 10/11/12 6:31 PM:
---------------------------------------------------------------

Fair enough, reusability will be the default for Channels not implemented for 
sinks/sources.

I am +1 on changing the name Reusable/NonReusable but I am -1 on Stateful and 
Stateless. The "State" term feels too close to the actual programming meaning 
of Stateless where as all the channels clearly have state. Perhaps Recycleable 
and Disposable? Or maybe just StatefulChannel StatelessChannel? 
                
      was (Author: brocknoland):
    Fair enough, reusability will be the default for Channels but be 
implemented for sinks/sources.

I am +1 on changing the name Reusable/NonReusable but I am -1 on Stateful and 
Stateless. The "State" term feels too close to the actual programming meaning 
of Stateless where as all the channels clearly have state. Perhaps Recycleable 
and Disposable? Or maybe just StatefulChannel StatelessChannel? 
                  
> Flume configuration code could be improved
> ------------------------------------------
>
>                 Key: FLUME-1630
>                 URL: https://issues.apache.org/jira/browse/FLUME-1630
>             Project: Flume
>          Issue Type: Sub-task
>          Components: Configuration
>    Affects Versions: v1.3.0
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>         Attachments: FLUME-1630-0.patch, FLUME-1630-1.patch
>
>
> 1) It's not currently possible to provide your own configuration source
> 2) All sinks/sources/channels are reused, even across re-configurations which 
> they are not used
> 3) The flume-ng-node module is very complex and starts many threads which are 
> not required. That is there are multiple life cycle supervisors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to