You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2016/07/18 12:23:20 UTC
[jira] [Commented] (ACCUMULO-4376) Introduce a KeyBuilder class
[ https://issues.apache.org/jira/browse/ACCUMULO-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382194#comment-15382194 ]
Keith Turner commented on ACCUMULO-4376:
----------------------------------------
For the sake of design consistency, I think it would be best to create builders for all of the Accumulo data classes (Mutation, Range, Key) at once.
> Introduce a KeyBuilder class
> ----------------------------
>
> Key: ACCUMULO-4376
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4376
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: Josh Elser
> Fix For: 1.9.0
>
>
> In looking at ACCUMULO-4375, I was a little frustrated at how we have 3x constructors than Key really provides just to support {{byte[]}}, {{Text}}, and {{CharSequence}} arguments. Additionally, the {{copy}} argument forces the user to use the most specific (most arguments) constructor if they want to avoid the copy. This makes constructing a Key from just a row while avoiding a copy very pedantic.
> I think a KeyBuilder (or KeyFactory) class would be a big usability benefit and reduce the amount of code that clients have to write to most efficiently construct Keys.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)