[
https://issues.apache.org/jira/browse/HBASE-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HBASE-831:
--------------------------------
Resolution: Fixed
Fix Version/s: 0.3.0
0.2.1
Status: Resolved (was: Patch Available)
Committed to 0.2 branch and trunk. Thanks for the patch Andrew!
> 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
> Fix For: 0.2.1, 0.3.0
>
> 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.
