Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 31 Jul 2011 16:38:09 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1566110090.21809.1312130289590.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <61342584.19728.1311969610718.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4148) HFileOutputFormat doesn't fill in
 TIMERANGE_KEY metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HBASE-4148:
------------------------------------

Looks like the current patch only applies against 0.90. Can you make one for trunk too?

> 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-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