hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13441) Scan API improvements
Date Tue, 21 Apr 2015 22:22:00 GMT

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

stack commented on HBASE-13441:
-------------------------------

Good one [~jonathan.lawlor] Suggest you give the current Scan API a review. Sounds like caching/batching
and even size-of-result no longer makes sense given the work you've done to date in scan operations
so lets purge/deprecate methods to do with size and batch.  Are there other methods we can
clean up?

What is that setMaxResultsPerColumnFamily method about? Seems odd. At a minimum could do w/
better javadoc.

Ditto setRowOffsetPerColumnFamily


> Scan API improvements
> ---------------------
>
>                 Key: HBASE-13441
>                 URL: https://issues.apache.org/jira/browse/HBASE-13441
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Jonathan Lawlor
>
> Umbrella task for improvements that could be made to the Scan API



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

Mime
View raw message