[
https://issues.apache.org/jira/browse/HBASE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-1990:
----------------------------------
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.
was:
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.
Priority: Minor (was: Major)
Fix Version/s: 0.20.3
0.21.0
Assignee: Andrew Purtell
> Add methods accepting strings for family/qualifier in client
> -------------------------------------------------------------
>
> Key: HBASE-1990
> URL: https://issues.apache.org/jira/browse/HBASE-1990
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.20.0
> Reporter: Doug Meil
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.21.0, 0.20.3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
