You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 17:05:00 UTC

[jira] [Closed] (HBASE-6379) [0.90 branch] Backport HBASE-6334 to 0.90

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

Andrew Kyle Purtell closed HBASE-6379.
--------------------------------------

> [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: Improvement
>          Components: test
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>            Priority: Major
>             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 was sent by Atlassian Jira
(v8.20.7#820007)