You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jesse Yates (JIRA)" <ji...@apache.org> on 2012/06/30 18:34:44 UTC

[jira] [Assigned] (HBASE-6296) Refactor EventType to track its own ExecutorService type

     [ https://issues.apache.org/jira/browse/HBASE-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesse Yates reassigned HBASE-6296:
----------------------------------

    Assignee: Jesse Yates
    
> Refactor EventType to track its own ExecutorService type
> --------------------------------------------------------
>
>                 Key: HBASE-6296
>                 URL: https://issues.apache.org/jira/browse/HBASE-6296
>             Project: HBase
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 0.96.0
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>            Priority: Minor
>             Fix For: 0.96.0
>
>         Attachments: java_hbase-6296-v0.patch
>
>
> Currently there is a massive switch statement in org.apache.hadoop.hbase.executor.ExecutorService for the ExecutorType for each org.apache.hadoop.hbase.executor.EventHandler.EventType. This means is you add an new event type, you will also have to change the executorservice file, if for nothing but to add the executor type. Instead the EventType should just be able to keep track of which executor it should use.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira