[
https://issues.apache.org/jira/browse/ACCUMULO-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157548#comment-16157548
]
Josh Elser commented on ACCUMULO-2445:
--------------------------------------
I can echo Christopher's comments about ByteBuffer being a pain to work with. I
wouldn't want to push that onto users as the only option. Didn't [~kturner]
make some kind of helper class for bytes that we could leverage?
I did want to mention: there is a bit of value that we could recognize
server-side by using ByteBuffers, notably around the ability to create
"off-heap" (direct) ByteBuffers. Making this kind of change internally would
pave the way for future improvements which can help limit the impact of JVM GC
and improve our overall latency.
> 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)
