accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1005) Authorizations and ColumnVisibility API should not accept Charset param
Date Tue, 07 May 2013 02:55:18 GMT


Hudson commented on ACCUMULO-1005:

Integrated in Accumulo-1.5 #98 (See [])
    ACCUMULO-1005 Applying patch contributed by Tim Reardon to remove Charset options from
Authorizations and ColumnVisibility, with minor edits from John Vines and minor documentation
additions and cleanup from myself (Revision 1479039)

     Result = SUCCESS
ctubbsii : 
Files : 
* /accumulo/branches/1.5/core/src/main/java/org/apache/accumulo/core/security/
* /accumulo/branches/1.5/core/src/main/java/org/apache/accumulo/core/security/
* /accumulo/branches/1.5/core/src/test/java/org/apache/accumulo/core/security/
* /accumulo/branches/1.5/core/src/test/java/org/apache/accumulo/core/security/
* /accumulo/branches/1.5/core/src/test/java/org/apache/accumulo/core/security/

> Authorizations and ColumnVisibility API should not accept Charset param
> -----------------------------------------------------------------------
>                 Key: ACCUMULO-1005
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Christopher Tubbs
>            Assignee: Tim Reardon
>             Fix For: 1.5.0
>         Attachments: ACCUMULO-1005_deprecate.patch, ACCUMULO-1005.patch
> The Charset parameter was added to the public API for ACCUMULO-241. However, this intermingles
internal serialization/comparison implementation, and the semantics of the public API.
> The Charset parameter effectively instructs Accumulo how to serialize the object. This
can break the comparison with what is stored in the table and is an unnecessary breakage.
> In the public API, we should only accept Strings, and allow any valid java String. Internally,
the serialization of these should consistently be UTF-8.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message