Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 22 Mar 2014 01:04:43 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12701966.1395086138963.123114.1395450283935@arcas>
In-Reply-To: <JIRA.12701966.1395086138963@arcas>
References: <JIRA.12701966.1395086138963@arcas>
Subject: [jira] [Resolved] (ACCUMULO-2487) Value implementation provides
 conflicting statements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey resolved ACCUMULO-2487.
-----------------------------------

    Resolution: Fixed

> 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
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 1.6.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)