hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Malaska (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14795) Provide an alternative spark-hbase SQL implementations for Scan
Date Tue, 10 Nov 2015 23:54:10 GMT

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

Ted Malaska commented on HBASE-14795:
-------------------------------------

There is no real negative to this proposed approach other then a second implementation of
table scan.  To bad the existing TableInputFormat can not be updated to handle this because
then this would be in one local.

As for implementation these is no reason this can't just be invoked straight from line 330
from DefaultSource or could be an alternate implementation in hbaseRDD that tables multi scan
objects. 

https://github.com/apache/hbase/blob/master/hbase-spark/src/main/scala/org/apache/hadoop/hbase/spark/DefaultSource.scala#L330


> Provide an alternative spark-hbase SQL implementations for Scan
> ---------------------------------------------------------------
>
>                 Key: HBASE-14795
>                 URL: https://issues.apache.org/jira/browse/HBASE-14795
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Malaska
>            Assignee: Zhan Zhang
>            Priority: Minor
>
> This is a sub-jira of HBASE-14789.  This jira is to focus on the replacement of TableInputFormat
for a more custom scan implementation that will make the following use case more effective.
> Use case:
> In the case you have multiple scan ranges on a single table with in a single query. 
TableInputFormat will scan the the outer range of the scan start and end range where this
implementation can be more pointed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message