Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 22 Aug 2011 10:05:29 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1350240627.675.1314007529206.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1775242191.50084.1313694329302.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HBASE-4225) NoSuchColumnFamilyException in multi
 doesn't say which family is bad
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ramkrishna.s.vasudevan reassigned HBASE-4225:
---------------------------------------------

    Assignee: ramkrishna.s.vasudevan

> NoSuchColumnFamilyException in multi doesn't say which family is bad
> --------------------------------------------------------------------
>
>                 Key: HBASE-4225
>                 URL: https://issues.apache.org/jira/browse/HBASE-4225
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>             Fix For: 0.90.5
>
>
> It's kind of a dumb one, in HRegion.doMiniBatchPut we do:
> {code}
> LOG.warn("No such column family in batch put", nscf);
> batchOp.retCodes[lastIndexExclusive] = OperationStatusCode.BAD_FAMILY;
> {code}
> So we lose the family here, all we know is there's a bad one, that's what's in HRS.multi:
> {code}
> } else if (code == OperationStatusCode.BAD_FAMILY) {
>   result = new NoSuchColumnFamilyException();
> {code}
> We can't just throw the exception like that, we need to say which one is bad even if it requires testing all passed MultiActions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira