[ https://issues.apache.org/jira/browse/HIVE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886541#action_12886541 ]
John Sichi commented on HIVE-1245: ---------------------------------- For atomic types, we could extend the column-level mapping directive to allow for three options * string * binary * use table-level default So where we currently have a:b, we would support a:b:string and a:b:binary. The table-level default would be set in a separate serde property hbase.storedtype.atomic, with a default value of string for backwards-compatibility. Then something similar for compound types, but with json and delimited as options? I haven't thought about all the combinations, and what to do with column familiies. > allow access to values stored as non-strings in HBase > ----------------------------------------------------- > > Key: HIVE-1245 > URL: https://issues.apache.org/jira/browse/HIVE-1245 > Project: Hadoop Hive > Issue Type: Improvement > Components: HBase Handler > Affects Versions: 0.6.0 > Reporter: John Sichi > Assignee: John Sichi > > See test case in > http://mail-archives.apache.org/mod_mbox/hadoop-hive-user/201003.mbox/browser -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.