[
https://issues.apache.org/jira/browse/ACCUMULO-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984456#comment-13984456
]
ASF subversion and git services commented on ACCUMULO-2748:
-----------------------------------------------------------
Commit ff8c2383bbd394dadffa669518da53e37d0122e5 in accumulo's branch
refs/heads/1.5.2-SNAPSHOT from [~mikebfagan]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=ff8c238 ]
ACCUMULO-2748 added logic to handle null keys for MockTableOperations.deleteRow
Signed-off-by: Josh Elser <[email protected]>
> MockTableOperations.deleteRow does not handle null for start or end keys
> ------------------------------------------------------------------------
>
> Key: ACCUMULO-2748
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2748
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Affects Versions: 1.5.1, 1.6.0
> Environment: OSX Mavericks
> Reporter: Mike Fagan
> Assignee: Mike Fagan
> Priority: Critical
> Labels: noob, test
> Fix For: 1.5.2, 1.6.1
>
> Attachments: ACCUMULO-2748.patch
>
>
> The deleteRow function does not check for null values for start or end keys.
> These null values are passed down into key constructor which will throw a
> NullPointerException:
> java.lang.NullPointerException
> at org.apache.accumulo.core.data.Key.<init>(Key.java:103)
> at
> org.apache.accumulo.core.client.mock.MockTableOperations.deleteRows(MockTableOperations.java:315)
> The API semantics dictate:
> if (start == null ) then start == Text()
> if (end == null ) then end == maxKey()
--
This message was sent by Atlassian JIRA
(v6.2#6252)
