hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8534) fix coverage org.apache.hadoop.hbase.mapreduce
Date Thu, 30 May 2013 19:49:20 GMT

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

Nick Dimiduk commented on HBASE-8534:
-------------------------------------

bq. Lastly, using System.exit is often an anti pattern, could it be the root cause of the
problem?

That's really the root of the issue. IIRC, this is the same thing that complicates HBASE-8367.

I'm not sure what the implications of SUREFIRE-767 mean. @Aleksey's original SecurityManager
patch appeared to run correctly.

I guess I'd prefer to see the SecurityManager implementation, minus the stateful constructor
as the least-invasive. We can followup with a general purge of System.exit if that remains
a pressing issue.

Sorry for the churn, Aleksey. Would you mind also updating HBASE-8611 so as to use same implementation?
                
> fix coverage org.apache.hadoop.hbase.mapreduce
> ----------------------------------------------
>
>                 Key: HBASE-8534
>                 URL: https://issues.apache.org/jira/browse/HBASE-8534
>             Project: HBase
>          Issue Type: Test
>    Affects Versions: 0.94.8, 0.95.2
>            Reporter: Aleksey Gorshkov
>            Assignee: Aleksey Gorshkov
>         Attachments: HBASE-8534-0.94-d.patch, HBASE-8534-0.94-e.patch, HBASE-8534-0.94-f.patch,
HBASE-8534-0.94.patch, HBASE-8534-trunk-a.patch, HBASE-8534-trunk-b.patch, HBASE-8534-trunk-c.patch,
HBASE-8534-trunk-d.patch, HBASE-8534-trunk-e.patch, HBASE-8534-trunk-f.patch, HBASE-8534-trunk.patch
>
>
> fix coverage org.apache.hadoop.hbase.mapreduce
> patch HBASE-8534-0.94.patch for branch-0.94
> patch HBASE-8534-trunk.patch for branch-0.95 and trunk

--
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

Mime
View raw message