phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-418) Support approximate COUNT DISTINCT
Date Fri, 25 Aug 2017 03:11:00 GMT


Josh Elser commented on PHOENIX-418:

[~jamestaylor], thanks for thinking about the licensing! Turns out, there is something that
we should propagate in the binary tarball

Specifically, we should include text, something like:

Copyright 2016 AddThis

This product includes software developed by AddThis.

Aside, it appears that there is a 2.9.5 version of {{}} in
maven-central. Is there a reason for us to use 2.7.0, specifically?

Neat little change, Ethan. I look forward to playing around with the feature :)

> Support approximate COUNT DISTINCT
> ----------------------------------
>                 Key: PHOENIX-418
>                 URL:
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>            Assignee: Ethan Wang
>              Labels: gsoc2016
>         Attachments: PHOENIX-418-v1.patch, PHOENIX-418-v2.patch, PHOENIX-418-v3.patch,
PHOENIX-418-v4.patch, PHOENIX-418-v5.patch, PHOENIX-418-v6.patch
> Support an "approximation" of count distinct to prevent having to hold on to all distinct
values (since this will not scale well when the number of distinct values is huge). The Apache
Drill folks have had some interesting discussions on this [here](
They recommend using  [Welford's method](
I'm open to having a config option that uses exact versus approximate. I don't have experience
implementing an approximate implementation, so I'm not sure how much state is required to
keep on the server and return to the client (other than realizing it'd be much less that returning
all distinct values and their counts).

This message was sent by Atlassian JIRA

View raw message