You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mario Pastorelli (JIRA)" <ji...@apache.org> on 2016/08/27 13:52:20 UTC
[jira] [Comment Edited] (ACCUMULO-4376) Introduce a Builders for
"data" classes
[ https://issues.apache.org/jira/browse/ACCUMULO-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15441586#comment-15441586 ]
Mario Pastorelli edited comment on ACCUMULO-4376 at 8/27/16 1:52 PM:
---------------------------------------------------------------------
There are a lot of important things in ACCUMULO-2589 but nothing related to how Keys and other structures are created. Are you talking about some specific task/comment of that JIRA?
was (Author: melrief):
Ther are a lot of important things in ACCUMULO-2589 but nothing related to how Keys and other structures are created. Are you talking about some specific task/comment of that JIRA?
> Introduce a Builders for "data" classes
> ---------------------------------------
>
> Key: ACCUMULO-4376
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4376
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: Josh Elser
> Fix For: 2.0.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)