You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Lars George <la...@gmail.com> on 2013/07/16 10:36:03 UTC
Fwd: [jira] [Commented] (HBASE-8943) Split Thrift2's ThriftServer into separate classes for easier testing and modularization
Did this get committed with the wrong JIRA number?
Begin forwarded message:
> From: "Hudson (JIRA)" <ji...@apache.org>
> Subject: [jira] [Commented] (HBASE-8943) Split Thrift2's ThriftServer into separate classes for easier testing and modularization
> Date: July 16, 2013 2:44:55 AM GMT+02:00
> To: issues@hbase.apache.org
>
>
> [ https://issues.apache.org/jira/browse/HBASE-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709294#comment-13709294 ]
>
> Hudson commented on HBASE-8943:
> -------------------------------
>
> FAILURE: Integrated in hbase-0.95-on-hadoop2 #180 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/180/])
> HBASE-8943 TestRegionMergeTransactionOnCluster#testWholesomeMerge may fail due to race in opening region (stack: rev 1503471)
> * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/DispatchMergingRegionHandler.java
>
>
>> Split Thrift2's ThriftServer into separate classes for easier testing and modularization
>> ----------------------------------------------------------------------------------------
>>
>> Key: HBASE-8943
>> URL: https://issues.apache.org/jira/browse/HBASE-8943
>> Project: HBase
>> Issue Type: Sub-task
>> Components: Thrift
>> Reporter: Lars George
>> Assignee: Lars George
>> Labels: thrift2
>>
>> Currently the ThriftServer class in Thrift 2 sets up and starts the actual server. Better follow a similar pattern to Thrift 1 where there is some factory setting up the server, and a separate start section. That way it is easier to test if the setup of the server is picking up everything it needs.
>
> --
> 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