[
https://issues.apache.org/jira/browse/HBASE-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762075#comment-13762075
]
Ivan A. Veselovsky commented on HBASE-8534:
-------------------------------------------
Hi, Nick,
I will be responsible for this in place of Alexey G.
As far as I understand, a separate issue was created to backport this fix to
0.94 branch.
Initially all these coverage fixes were intended to go to 3 branches: trunk,
0.95, 0.94.
So, what about backporting of this change to 0.95 also?
Currently I see it in trunk only:
{code}
$ cd ../hbase-0.94/
svn log . | grep -C 2 -- '-8534'
$ cd ../hbase-0.95/
$ svn log . | grep -C 2 -- '-8534'
$ cd ../hbase-trunk/
$ svn log . | grep -C 2 -- '-8534'
r1489878 | tedyu | 2013-06-05 17:56:49 +0400 (Wed, 05 Jun 2013) | 3 lines
HBASE-8534 addendum removes TestDriver (Nick Dimiduk)
--
r1488542 | tedyu | 2013-06-01 20:23:55 +0400 (Sat, 01 Jun 2013) | 3 lines
HBASE-8534 Fix coverage for org.apache.hadoop.hbase.mapreduce (Aleksey Gorshkov)
{code}
> Fix coverage for org.apache.hadoop.hbase.mapreduce
> --------------------------------------------------
>
> Key: HBASE-8534
> URL: https://issues.apache.org/jira/browse/HBASE-8534
> Project: HBase
> Issue Type: Test
> Components: mapreduce, test
> Affects Versions: 0.94.8, 0.95.2
> Reporter: Aleksey Gorshkov
> Assignee: Aleksey Gorshkov
> Fix For: 0.98.0
>
> Attachments: 0001-HBASE-8534-hadoop2-addendum.patch,
> 8534-trunk-h.patch, HBASE-8534-0.94-d.patch, HBASE-8534-0.94-e.patch,
> HBASE-8534-0.94-f.patch, HBASE-8534-0.94-g.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-g.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
