[
https://issues.apache.org/jira/browse/ACCUMULO-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383029#comment-15383029
]
Josh Elser commented on ACCUMULO-4376:
--------------------------------------
Talked about this a little more with Keith in #accumulo today. I think the list
of Builders we would want to create would be:
* Key
* Mutation
* Range
* ConditionalMutation
* Condition
Potentially also, although I think these are lesser since they're not often
used by users (but used behind the client-api scene)
* Column
* ColumnUpdate
We can certainly break these out into sub-tasks and share the work. We should
just try to introduce them into a release at the same time.
> 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: 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)
