You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2008/08/14 19:53:44 UTC
[jira] Updated: (HBASE-831) committing BatchUpdate with no row
should complain
[ https://issues.apache.org/jira/browse/HBASE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-831:
---------------------------------
Assignee: Andrew Purtell
Status: Patch Available (was: Open)
> committing BatchUpdate with no row should complain
> --------------------------------------------------
>
> Key: HBASE-831
> URL: https://issues.apache.org/jira/browse/HBASE-831
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Michael Bieniosek
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: 831.patch
>
>
> Running this code:
> BatchUpdate update = new BatchUpdate();
> update.put(key, value);
> table.commit(update);
> Down in getRegionServer, this triggers an NPE because the row is null (which I saw because I was running in a debugger); this NPE gets retried somewhere in the bowels of IPC. Instead, we should either remove the zero-arg BatchUpdate constructor, or have table.commit throw a runtimeexception if the row is null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.