[ https://issues.apache.org/jira/browse/ACCUMULO-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449809#comment-15449809 ]
Keith Turner commented on ACCUMULO-4376: ---------------------------------------- [~melrief] if you are thinking of working, consider reading the following article. I like this approach of using interfaces to define the builder graph and having a implementation builder class that implements all of the interfaces. https://www.jayway.com/2012/02/07/builder-pattern-with-a-twist/ > 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)