accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-2487) Value implementation provides conflicting statements
Date Mon, 17 Mar 2014 19:55:47 GMT
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)

Mime
View raw message