[
https://issues.apache.org/jira/browse/HIVE-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030369#comment-14030369
]
Sushanth Sowmyan commented on HIVE-6584:
----------------------------------------
Teng, I'd be interested in how your patch winds up being.
If you mean that at runtime, the HBaseStorageHandler decides to deputize a
subclass of itself to do the work, then that might work. But if you mean that
your approach would lead to the user having to create a separate table (kinda
like a view) that associates with a snapshot, then speaking from the hive side,
I think I would prefer having only one SH to deal with, and having it decide
what to do with various set parameters as opposed to creating separate hive
tables with a different SH in hive. That way, using the same hive table
definition, a query could decide to use a snapshot or not.
> Add HiveHBaseTableSnapshotInputFormat
> -------------------------------------
>
> Key: HIVE-6584
> URL: https://issues.apache.org/jira/browse/HIVE-6584
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.14.0
>
> Attachments: HIVE-6584.0.patch, HIVE-6584.1.patch, HIVE-6584.2.patch,
> HIVE-6584.3.patch
>
>
> HBASE-8369 provided mapreduce support for reading from HBase table snapsopts.
> This allows a MR job to consume a stable, read-only view of an HBase table
> directly off of HDFS. Bypassing the online region server API provides a nice
> performance boost for the full scan. HBASE-10642 is backporting that feature
> to 0.94/0.96 and also adding a {{mapred}} implementation. Once that's
> available, we should add an input format. A follow-on patch could work out
> how to integrate this functionality into the StorageHandler, similar to how
> HIVE-6473 integrates the HFileOutputFormat into existing table definitions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
