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-3904) Queries with LIKE and LIMIT OFFSET fail for mutable tables with column mapping enabled
Date Fri, 02 Jun 2017 17:52:04 GMT

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

James Taylor commented on PHOENIX-3904:
---------------------------------------

[~samarth.jain@gmail.com] - Yes, you'd need to project the empty key value if everything is
being projected. One question about this code:
{code}
+                        for (int i = start; i <= end; i++) {
+                            qualifierSet.add(table.getEncodingScheme().encode(i));
+                        }
{code}
Wouldn't this project all cq, even for columns that had previously been dropped? Would it
be better to iterate through the columns using {{table.getColumnFamily(familyName).getColumns()}}?

> Queries with LIKE and LIMIT OFFSET fail for mutable tables with column mapping enabled
> --------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3904
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3904
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>             Fix For: 4.11.0
>
>         Attachments: PHOENIX-3904.patch, PHOENIX-3904_v2.patch, PHOENIX-3904_v3.patch,
PHOENIX-3904_v4.patch, PHOENIX-3904_v5.patch
>
>
> Details:
> https://stackoverflow.com/questions/44214659/qualifier-out-of-valid-range-error-in-apache-phoenix-select-with-where-and-of



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

Mime
View raw message