phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Xu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-3392) SortMergeJoinIT#testSubJoin[0] is failing with encodecolumns2 branch
Date Thu, 01 Jun 2017 07:47:04 GMT

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

Allen Xu edited comment on PHOENIX-3392 at 6/1/17 7:46 AM:
-----------------------------------------------------------

I have encountered this "qualifier out of range" problem with query like
select * from myns.test where "cf"."col1" like '%name2%' limit 10 offset 10

Please check stackoverflow: https://stackoverflow.com/questions/44214659/qualifier-out-of-valid-range-error-in-apache-phoenix-select-with-where-and-of

Thanks.


was (Author: allen_xu):
I have encountered this "qualifier out of range problem" with query like
select * from myns.test where "cf"."col1" like '%name2%' limit 10 offset 10

Please check stackoverflow: https://stackoverflow.com/questions/44214659/qualifier-out-of-valid-range-error-in-apache-phoenix-select-with-where-and-of

Thanks.

> SortMergeJoinIT#testSubJoin[0] is failing with encodecolumns2 branch
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-3392
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3392
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> The SortMergeJoinIT#testSubJoin[0] is failing with encodecolumns2 branch. To repro, checkout
the encodecolumns2 branch and run the SortMergeJoinIT tests. Here's the stack trace is here:
https://builds.apache.org/job/Phoenix-encode-columns/16/testReport/org.apache.phoenix.end2end/SortMergeJoinIT/testSubJoin_0_/
> The basic idea of column encoding over mutable tables is that we take control of the
column qualifier name, storing in PColumn the mapping of real column name to column qualifier
name. We use serialized integers as the column qualifier names so that we can do positional
lookups into the List<Cell> we get back from HBase APIs. There are a few "reserved"
column qualifiers for things like our empty key value, etc. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message