[
https://issues.apache.org/jira/browse/HBASE-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793417#action_12793417
]
stack commented on HBASE-2051:
------------------------------
In the code you have so far, the Spring dependency looks like it could be
undone since only used in one place for minor benefit (least as I read it). In
general, we've not prob. adding new jars when tit makes life easier(all
additions are minor hiding in the shadow of the fat jruby complete jar).
Anything that makes hbase easier to use, we're game for.
We're a bit behind but its looking like hadoop jars wil be up in apache maven
repo. before too long. HBase should follow suit.
I think the google code route a good way to go at first at least. I'd suggest
you talk up your progress over in hbase-dev to keep your work in the spotlight
-- it might help you get recruits whether users or co-devs.
Thanks.
> Use builder pattern to improve usability of client API
> ------------------------------------------------------
>
> Key: HBASE-2051
> URL: https://issues.apache.org/jira/browse/HBASE-2051
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Fix For: 0.21.0
>
> Attachments: aconex-hbase-utils.zip
>
>
> From Paul Smith up on hbase-user@:
> {quote}
> I think a good collection of useful builders and utilities that handle the
> 80% case will help HBase gain much more traction. As an person starting with
> HBase, there are a lot of concepts to get, Bytes definitely get in the way of
> seeing the real underlying patterns. I'm a total believer in understanding
> the internals to get the best out of a product, but that often comes after
> experimentation, and these high-level libraries grease the wheels for faster
> 'grok'ing the concepts.
> Thinking out loud here, but something like this may be useful:
> {code}
> PutBuilder builder = new PutBuilder(hTable);
> // first Row
> builder.withRowKey(1stRowKey).withColumnFamily("foo")
> .put("columnA", valueA)
> .put("columnB",valueB);
> // secondRow
> builder.withRowKey(2ndRowKey).withColumnFamily("eek")
> .put("columnC", valueC)
> .put("columnD",valueD);
> ..
> builder.putAll();
> {code}
> {quote}
> Perhaps we could use the Builder pattern to achieve simplification (e.g.
> HBASE-1990) and API support for multicalls (HBASE-1986, HBASE-1845) at the
> same time. Method variants should accept byte[] or String for keys or values,
> and lists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
