hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6379) [0.90 branch] Backport HBASE-6334 to 0.90
Date Thu, 12 Jul 2012 23:35:35 GMT

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

Gregory Chanan updated HBASE-6379:

    Attachment: HBASE-6379.patch

* Attached HBASE-6379.patch *

This is a pretty straightforward backport of HBASE-6334, with the addition of only checking
errors *within* a column family (see description above).

NOTE: This is built on top of HBASE-6385, which also changes TestHRegion, so cannot be checked
in before that.
> [0.90 branch] Backport HBASE-6334 to 0.90
> -----------------------------------------
>                 Key: HBASE-6379
>                 URL: https://issues.apache.org/jira/browse/HBASE-6379
>             Project: HBase
>          Issue Type: Task
>          Components: test
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 0.90.7
>         Attachments: HBASE-6379.patch
> See HBASE-6334 for details.
> The issue is that HBASE-6334 detects both HBASE-4195 (which should be backported to 0.90
-- I'll file another JIRA for that) and HBASE-2856 (which is a known issue in 0.90 that won't
be fixed because it requires a change to the HFile format).  So in 0.90, we need a way to
only catch HBASE-4195 failures and ignore HBASE-2856 failures.
> Luckily, HBASE-4195 only occurs *within* a column family, while HBASE-2856 occurs *between*
column families, so we just need to add a little to the backport to differentiate.

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


View raw message