phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3866) COUNT(col) should scan along required column families only
Date Thu, 25 May 2017 16:25:04 GMT

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

Lars Hofhansl commented on PHOENIX-3866:
----------------------------------------

Hi [~gsbiju], the table was defined like this:
{{create table test (mykey integer not null primary key, A.COLA integer, B.COLB integer) IMMUTABLE_ROWS=true,
STORE_NULL=false, IMMUTABLE_STORAGE_SCHEME = ONE_CELL_PER_COLUMN, DISABLE_WAL=true}}

Thanks for looking. Was going to look at this later myself, but didn't find much time.

> COUNT(col) should scan along required column families only
> ----------------------------------------------------------
>
>                 Key: PHOENIX-3866
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3866
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>            Priority: Minor
>
> These two should be equivalent:
> {code}
> 0: jdbc:phoenix:localhost> select count(B.COLB) from test;
> +----------------+
> | COUNT(B.COLB)  |
> +----------------+
> | 10054          |
> +----------------+
> 1 row selected (9.446 seconds)
> 0: jdbc:phoenix:localhost> select count(B.COLB) from test where B.COLB is not null;
> +----------------+
> | COUNT(B.COLB)  |
> +----------------+
> | 10054          |
> +----------------+
> 1 row selected (0.028 seconds)
> {code}
> Clearly the plain COUNT is doing unnecessary work.



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

Mime
View raw message