You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2010/01/07 09:40:04 UTC

[jira] Commented: (HBASE-2095) TableInputFormat should support more confs for the scanner

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

Lars George commented on HBASE-2095:
------------------------------------

Hey Bassam,

I did the BASE64 encoding back then because of the same reason you are facing now, i.e. the scan has so many options and subclasses that the easiest was to encode it as a serialized object and recreate it on the other end. I thought about a similar set of options but when arriving at the filters I stopped and went the different route. But as long as yours is an alternative to the fully specified Scan then all well.

Lars

> TableInputFormat should support more confs for the scanner
> ----------------------------------------------------------
>
>                 Key: HBASE-2095
>                 URL: https://issues.apache.org/jira/browse/HBASE-2095
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: mapreduce
>    Affects Versions: 0.20.2
>            Reporter: Bassam Tabbara
>             Fix For: 0.20.3
>
>         Attachments: HBASE-2095.patch
>
>
> TableInputFormat currently only supports hbase.mapreduce.scan and hbase.mapreduce.inputtable confs. The scan conf is a Base64 encoded scanner object, which makes it difficult to use TIF from hadoop pipes. I propose that the following confs be supported iff hbase.mapreduce.scan is not set:
> * hbase.mapreduce.scan.columns
> * hbase.mapreduce.scan.timestamp
> * hbase.mapreduce.scan.timerange.start
> * hbase.mapreduce.scan.timerange.end
> * hbase.mapreduce.scan.maxversions
> * hbase.mapreduce.scan.cacheblocks
> * hbase.mapreduce.scan.cachedrows
> Ideally we would also support filters but I think that would be harder to implement.

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