Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 26 Aug 2015 22:37:45 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12859444.1440623990000.176062.1440628665836@Atlassian.JIRA>
In-Reply-To: <JIRA.12859444.1440623990000@Atlassian.JIRA>
References: <JIRA.12859444.1440623990000@Atlassian.JIRA>
 <JIRA.12859444.1440623990820@arcas>
Subject: [jira] [Commented] (CASSANDRA-10203)
 UnbufferedDataOutputstreamPlus.writeUTF fails for 0 length and > 8190
 length strings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715648#comment-14715648 ] 

Benedict commented on CASSANDRA-10203:
--------------------------------------

+1 for the fix to commit and get release rolling again, but after that, I think we can:

# Make the whole of that runLength logic a little clearer
# Take a look at why our randomised testing didn't catch this. It looks like we're constraining the domain of randomisation unnecessarily with the phrase "the very model of a modern major general ..." - which, while pleasing to the eye, can probably be revisited to improve the utility of the test.

> UnbufferedDataOutputstreamPlus.writeUTF fails for 0 length and > 8190 length strings
> ------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10203
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10203
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>             Fix For: 2.2.1, 3.0 beta 2
>
>
> No length is written for 0 length strings. Strings >8190 fail.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)