You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Doug Meil (JIRA)" <ji...@apache.org> on 2013/03/22 19:53:16 UTC

[jira] [Updated] (HBASE-8180) [refGuide] Addition to performance.xml - use byte-array constants for CF, Cols

     [ https://issues.apache.org/jira/browse/HBASE-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Meil updated HBASE-8180:
-----------------------------

    Description: 
I realized that we don't have anywhere in the refGuide to use byte-array constants for CF and Column names.  Doing this .getByte() in a loop (especially in a MapReduce job) is surprisingly expensive.  Adding to the performance chapter.  

I am also going to update the other code examples in the book, but in another ticket.

This is one of those "so obvious that it's not" kind of things.



  was:
I realized that we don't have anywhere in the refGuide to use byte-array constants for CF and Column names.  Adding to the performance chapter.  I am also going to update the other code examples in the book, but in another ticket.

This is one of those "so obvious that it's not" kind of things.



    
> [refGuide] Addition to performance.xml - use byte-array constants for CF, Cols
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-8180
>                 URL: https://issues.apache.org/jira/browse/HBASE-8180
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Doug Meil
>            Assignee: Doug Meil
>
> I realized that we don't have anywhere in the refGuide to use byte-array constants for CF and Column names.  Doing this .getByte() in a loop (especially in a MapReduce job) is surprisingly expensive.  Adding to the performance chapter.  
> I am also going to update the other code examples in the book, but in another ticket.
> This is one of those "so obvious that it's not" kind of things.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira