You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2014/03/17 20:55:47 UTC
[jira] [Created] (ACCUMULO-2487) Value implementation provides
conflicting statements
Mike Drob created ACCUMULO-2487:
-----------------------------------
Summary: Value implementation provides conflicting statements
Key: ACCUMULO-2487
URL: https://issues.apache.org/jira/browse/ACCUMULO-2487
Project: Accumulo
Issue Type: Bug
Components: client
Reporter: Mike Drob
Priority: Minor
The javadoc for the no-arg constructor for {{Value}} states that it "Creates a zero-size sequence." However, the implementation of get will error in this case.
{code}
public byte[] get() {
if (this.value == null) {
throw new IllegalStateException("Uninitialized. Null constructor " + "called w/o accompanying readFields invocation");
}
{code}
Either we need to change the javadoc to be more explicit or change the behaviour of various accessors in the class. I would consider both solutions to be breaking of the API contract since we are changing what clients can expect from us.
--
This message was sent by Atlassian JIRA
(v6.2#6252)