[
https://issues.apache.org/jira/browse/PHOENIX-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163236#comment-14163236
]
jay wong commented on PHOENIX-1267:
-----------------------------------
[~jamestaylor]
About isScanForbidden logic is not about topN, it's about order by. But i found
that the order by query sign for TOPN.
eg: we have a result like. assume that small scan query 100 results one query.
|key|col1|
|1|2|
|2|1|
|...|...|
|100|55|
|2|101|
when next query. it found the row which is rowkey is greater than the last
rowkey in the last page.
so the rowkey will be fall into a Infinite loop.
> Set scan.setSmall(true) when appropriate
> ----------------------------------------
>
> Key: PHOENIX-1267
> URL: https://issues.apache.org/jira/browse/PHOENIX-1267
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: jay wong
> Attachments: smallscan.patch, smallscan2.patch
>
>
> There's a nice optimization that has been in HBase for a while now to set a
> scan as "small". This prevents extra RPC calls, I believe. We should add a
> hint for queries that forces it to be set/not set, and make our best guess on
> when it should default to true.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
