phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3133) Investigate why offset queries with reverse scan take a long time
Date Mon, 01 Aug 2016 19:32:20 GMT

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

James Taylor commented on PHOENIX-3133:
---------------------------------------

Would you mind taking a look at this one for 4.8.1, [~ankit@apache.org]?

> Investigate why offset queries with reverse scan take a long time
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-3133
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3133
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>             Fix For: 4.8.1
>
>
> We need to workaround HBASE-16296 because users of Phoenix won't see the fix until at
least the fix makes it into a release version of HBase. Unfortunately, often times users are
forced to stick to earlier version of HBase, even after a release. PHOENIX-3121 works around
the issue when there's only a LIMIT clause. However, if there's a LIMIT and an OFFSET, the
issue still occurs. See PHOENIX-3121 for a repro.



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

Mime
View raw message