[ https://issues.apache.org/jira/browse/ACCUMULO-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey updated ACCUMULO-2487: ---------------------------------- Priority: Critical (was: Minor) I raised the priority to Critical because this issue impacts our API. > 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: Critical > Fix For: 1.7.0 > > > 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)