Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1174368314.1228874204575.JavaMail.jira@brutus>
Date: Tue, 9 Dec 2008 17:56:44 -0800 (PST)
From: "Clint Morgan (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-1054) Index NPE on scanning
In-Reply-To: <2084557668.1228869886317.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Clint Morgan updated HBASE-1054:
--------------------------------

    Summary: Index NPE on scanning  (was: Index descriptions are not copied in HTableDescriptor copy constructor)

> Index NPE on scanning
> ---------------------
>
>                 Key: HBASE-1054
>                 URL: https://issues.apache.org/jira/browse/HBASE-1054
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Clint Morgan
>            Assignee: Clint Morgan
>         Attachments: hbase-1054.patch
>
>
> I had some tables refuse to find their indexes even though they were defined and had been updated. Scanning .META. I see that some regions from the table don't have the indexes...
> Oddly, during  the .META. scan, I would see that I had 3 entries per table. (I have very little data in each table, def not splitting yet) But when I visited the UI it showed just one region per table...
> This patch also addes some toStrings that helped in diagnostics, and a new null check that I found I needed in IndexedTableScanner

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.