[ 
https://issues.apache.org/jira/browse/HBASE-12596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629915#comment-14629915
 ] 

Sean Busbey commented on HBASE-12596:
-------------------------------------

I don't plan to accept feature additions to 1.2.z after 1.2.0. However, I still 
haven't gotten 1.2.0 RC0 out (:sadpanda) so I don't consider it feature frozen. 
I'd be fine with this going in there so long as it's before RC0. I expect the 
licensing issues on HBASE-14085 to take long enough that an RC won't happen 
before tomorrow.

As an aside [~lhofhansl], if this issue goes into branch-1.2 leaving the 1.3.0 
version number in place is perfectly fine. As the RM I'll remove the 1.3.0 once 
I've made sure it's present on 1.2.0 and in the changelog (and fix the versions 
here if, for example, it had to be reverted before an RC got promoted to a 
release).

> bulkload needs to follow locality
> ---------------------------------
>
>                 Key: HBASE-12596
>                 URL: https://issues.apache.org/jira/browse/HBASE-12596
>             Project: HBase
>          Issue Type: Improvement
>          Components: HFile, regionserver
>    Affects Versions: 0.98.8
>         Environment: hadoop-2.3.0, hbase-0.98.8, jdk1.7
>            Reporter: Victor Xu
>            Assignee: Victor Xu
>             Fix For: 2.0.0, 0.98.14, 1.3.0
>
>         Attachments: HBASE-12596-0.98-v1.patch, HBASE-12596-0.98-v2.patch, 
> HBASE-12596-0.98-v3.patch, HBASE-12596-0.98-v4.patch, 
> HBASE-12596-0.98-v5.patch, HBASE-12596-0.98-v6.patch, 
> HBASE-12596-branch-1-v1.patch, HBASE-12596-branch-1-v2.patch, 
> HBASE-12596-master-v1.patch, HBASE-12596-master-v2.patch, 
> HBASE-12596-master-v3.patch, HBASE-12596-master-v4.patch, 
> HBASE-12596-master-v5.patch, HBASE-12596-master-v6.patch, HBASE-12596.patch
>
>
> Normally, we have 2 steps to perform a bulkload: 1. use a job to write HFiles 
> to be loaded; 2. Move these HFiles to the right hdfs directory. However, the 
> locality could be loss during the first step. Why not just write the HFiles 
> directly into the right place? We can do this easily because 
> StoreFile.WriterBuilder has the "withFavoredNodes" method, and we just need 
> to call it in HFileOutputFormat's getNewWriter().
> This feature is enabled by default, and we could use 
> 'hbase.bulkload.locality.sensitive.enabled=false' to disable it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to