hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6296) Refactor EventType to track its own ExecutorService type
Date Wed, 04 Jul 2012 20:59:34 GMT

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

stack updated HBASE-6296:
-------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Committed to trunk.  I ran tests locally w/ this patch applied and no failures or errors.
 Thanks for the clean up Jesse.
                
> 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: 6296v1.txt, 6296v1.txt, java_hbase-6296-v0.patch, 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

        

Mime
View raw message