[
https://issues.apache.org/jira/browse/ACCUMULO-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983645#comment-13983645
]
Sean Busbey commented on ACCUMULO-2748:
---------------------------------------
Thanks for the problem report Mike. Should I take the self assignment to mean
you're working on a patch?
> 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
> Fix For: 1.5.2, 1.6.1
>
>
> 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)
