[
https://issues.apache.org/jira/browse/HBASE-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075975#comment-13075975
]
Hudson commented on HBASE-4148:
-------------------------------
Integrated in HBase-TRUNK #2066 (See
[https://builds.apache.org/job/HBase-TRUNK/2066/])
HBASE-4148 HFileOutputFormat doesn't fill in TIMERANGE_KEY metadata
(Jonathan Hsieh)
tedyu :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/HFileOutputFormat.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFile.java
> HFileOutputFormat doesn't fill in TIMERANGE_KEY metadata
> --------------------------------------------------------
>
> Key: HBASE-4148
> URL: https://issues.apache.org/jira/browse/HBASE-4148
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.90.3
> Reporter: Todd Lipcon
> Assignee: Jonathan Hsieh
> Fix For: 0.90.5
>
> Attachments:
> 0001-HBASE-4148-HFileOutputFormat-doesn-t-fill-in-TIMERAN.patch,
> 0001-HBASE-4148-HFileOutputFormat-doesn-t-fill-in-TIMERAN.trunk.patch,
> 0001-HBASE-4148-HFileOutputFormat-doesn-t-fill-in-TIMERAN.trunk2.patch,
> 0001-HBASE-4148.-HFileOutputFormat-doesn-t-fill-in-TIMERA.patch
>
>
> When HFiles are flushed through the normal path, they include an attribute
> TIMERANGE_KEY which can be used to cull HFiles when performing a
> time-restricted scan. Files produced by HFileOutputFormat are currently
> missing this metadata.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
