[
https://issues.apache.org/jira/browse/HBASE-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538677#comment-13538677
]
Hadoop QA commented on HBASE-7206:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12562211/pre-hbase-7206.v6.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 94 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3666//console
This message is automatically generated.
> Foreign Exception framework v2 (simplifies and replaces HBASE-6571)
> -------------------------------------------------------------------
>
> Key: HBASE-7206
> URL: https://issues.apache.org/jira/browse/HBASE-7206
> Project: HBase
> Issue Type: Sub-task
> Components: snapshots
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: hbase-6055, 0.96.0
>
> Attachments: 121122-external-exceptions.pdf, hbase-7206.v3.patch,
> hbase-7206.v4.patch, hbase-7206.v6.patch, pre-hbase-7206.v4.patch,
> pre-hbase-7206.v6.patch
>
>
> This provides a way of sending exceptions from 'external' threads/processes
> (not the main executing thread) to others that poll cooperatively for
> external exceptions. Some examples of how this can be used include: having a
> separate timeout thread that injects an exception when a time limit has
> elapsed (TimeoutExceptionInjector, was OperationAttemptTimer), or having an
> exception from an separate process delivered to a local thread.
> This simplified version is centered around the ExternalException class.
> Instead of using generics and ErrorListener interfaces, this more
> straight-forward implementation eliminates many of the builders/factories and
> generics.
--
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
