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

Christopher Tubbs edited comment on ACCUMULO-4352 at 4/23/19 11:35 PM:
-----------------------------------------------------------------------

If this is still requested, please create a new issue or pull request to fix it 
at https://github.com/apache/accumulo/issues
Since we now have default methods available to us, because 2.0 and later use 
Java 8 (or later), this may be easier to handle today, rather than when this 
issue was first created.


was (Author: ctubbsii):
If this is still requested, please create a new issue or pull request to fix it 
at https://github.com/apache/accumulo/issues
Since we now have default methods available to us, because 2.0 and later use 
Java 8 (or later), this may be easier to handle.

> Lexicoder decode(byte[], offset, length) into public API
> --------------------------------------------------------
>
>                 Key: ACCUMULO-4352
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4352
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Shana Hutchison
>            Priority: Major
>
> I'm interested in calling {{decodeUnchecked(byte[], off, len)}} as public 
> API, since it removes the need to copy a subarray out from a larger array.  
> Currently the method sits in the {{AbstractEncoder}} class and is 
> {{protected}}.
> There was a discussion on ACCUULO-2817 to make decodeUnchecked public and add 
> it to the Lexicoder interface. The discussion involved a debate on binary 
> compatibility and semvar.  I can't tell what the resolution was.
> One option is to create a new interface extending Lexicoder with the new 
> method decodeUnchecked. It would maintain binary compatibility, at the cost 
> of adding another interface that exists only for binary compatibility 
> reasons. A few other options were suggested.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to