accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2445) API should use collection-of-bytes representation instead of Text
Date Fri, 08 Sep 2017 21:51:00 GMT


Christopher Tubbs commented on ACCUMULO-2445:

Big +1 to [~elserj]'s last comment. I think we want to move cautiously here.

Fluo Bytes is a WIP, that could be suitable to replace Text in future API changes, but it's
not yet done. Accumulo has its internal ByteSequence, and Fluo has its own current Bytes,
and there are others. I think Fluo Bytes will be a good candidate in the future, but in the
meantime, I don't know that we have any good options that aren't just going to create churn.

> API should use collection-of-bytes representation instead of Text
> -----------------------------------------------------------------
>                 Key: ACCUMULO-2445
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Sean Busbey
>            Assignee: Christopher Tubbs
>             Fix For: 2.0.0
> Right now we use Text as a container for bytes rather than as a UTF8 representation of
a string. This results in some gymnastics when people wish to use byte sequences that are
not valid UTF8 (see ACCUMULO-2437).
> We should use some representation of plain bytes (ideally byte[] or ByteBuffer) and deprecate
the use of Text so we can remove it later.

This message was sent by Atlassian JIRA

View raw message