[
https://issues.apache.org/jira/browse/ACCUMULO-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159074#comment-16159074
]
Josh Elser commented on ACCUMULO-2445:
--------------------------------------
I'm confused -- fluo-bytes is empty? There was never actually any code? Just an
idea?
I would just be concerned about using some class that we provide directly
without making sure it's really fleshed out. Mentioning fluo was just because I
assumed that such a "stable" bytes-centric API was already existing which we
could leverage. If that doesn't exist, we would just have to make sure what we
have now is stable/thorough.
> API should use collection-of-bytes representation instead of Text
> -----------------------------------------------------------------
>
> Key: ACCUMULO-2445
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2445
> 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
(v6.4.14#64029)
