Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <2146213.169821275606476747.JavaMail.jira@thor>
Date: Thu, 3 Jun 2010 19:07:56 -0400 (EDT)
From: "Ning Zhang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-1228) allow HBase key column to be anywhere
 in Hive table
In-Reply-To: <1909253348.186111268252787253.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875345#action_12875345 ] 

Ning Zhang commented on HIVE-1228:
----------------------------------

+1. had an offline review with John and everything looks fine. John is going to file 2 follow up JIRAs for negative test cases and generating splits based on selected columns.

Tests also passed just now. 

> allow HBase key column to be anywhere in Hive table
> ---------------------------------------------------
>
>                 Key: HIVE-1228
>                 URL: https://issues.apache.org/jira/browse/HIVE-1228
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: HBase Handler
>    Affects Versions: 0.6.0
>            Reporter: John Sichi
>            Assignee: John Sichi
>             Fix For: 0.6.0
>
>         Attachments: HIVE-1228.1.patch
>
>
> Current column mapping support requires key column to be first in Hive table (and implicit rather than explicit in column mapping).  We should allow it to be specified explicitly at any position within column mapping, e.g. with syntax :key to distinguish it from normal columns/families.
> Together with this, allow :timestamp column to be mapped.  For writes, this would allow timestamp to be explicitly provided by query (although we may want to prevent this in some cases; see for example HIVE-1223 and HIVE-1225).  For reads, this would allow timestamp to be fetched, and filters on timestamp could be used to find particular row versions.  (If no filter is supplied, should we return all row versions or only the default latest version?  The semantics need to be well-defined here.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.