[HBASE-1990] Add methods accepting strings for family/qualifier in client

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.20.0
• Component/s: Client
• Assignee: Unassigned
• Reporter: Doug Meil
• Created: 18/Nov/09 21:48
• Updated: 11/Jun/22 23:15
• Resolved: 12/May/14 00:40

Description

Consider the following client code...

byte b[] = result.getValue( Bytes.toBytes("family"), Bytes.toBytes("qualifier") );
put.add( Bytes.toBytes("family"), Bytes.toBytes("qualifer"), Bytes.toBytes( "value") );

... the requirement to supply family and qualifiers as bytes causes code to get cluttered and verbose. At worst, it scares peoples un-necessarily about HBase development, and at best, developers inevitably will get tired of doing all this casting and then add their own wrapper classes around the HBase client to make their code more readable.

I would like to see something like this in the API...

byte b[] = result.getValue( "family"), "qualifier" );
put.add( "family", "qualifer", Bytes.toBytes( "value") );

... where the Hbase client can perform the required Bytes.toBytes() conversion behind the scenes.

Issue Links

• is related to: HBASE-2051 Use builder pattern to improve usability of client API