Percentile calculations with Druid
Hi, I wanted to know which algorithm/s druid uses to compute percentile values. I came across this doc: http://druid.io/docs/latest/development/extensions-core/approximate-histograms.html but it mentions that there are "no formal error bounds on the approximation". So, just want to know what all options are available if one wishes to compute percentiles? Thanks in advance.
Creating 0.12.3-rc1
Hi all, I am creating 0.12.3-rc1 now, it should be available later today along with a draft of the release notes. Thanks, Jon
Re: Percentile calculations with Druid
Hi, I would look at data sketches as potentially a better alternative, with the recent release of "Numeric quantiles sketch aggregator" (As noted in the release notes: https://github.com/apache/incubator-druid/releases/druid-0.12.0). Unfortunately, the documentation wasn't ready with that release, thus is not available on the public website yet. It is marked to be released on the next major milestone (0.13.0) and viable on the Druid master branch: https://github.com/apache/incubator-druid/blob/master/docs/content/development/extensions-core/datasketches-quantiles.md On 2018/08/31 10:13:56, Abhishek Kaushik wrote: > Hi, > > I wanted to know which algorithm/s druid uses to compute percentile values. > I came across this doc: > http://druid.io/docs/latest/development/extensions-core/approximate-histograms.html > but it mentions that there are "no formal error bounds on the > approximation". So, just want to know what all options are available if one > wishes to compute percentiles? > > Thanks in advance. > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Percentile calculations with Druid
At my work, we have been using t-digest and yahoo quantile sketches for percentiles and building sketches. I am working on contributing the modules to the community. On Fri, Aug 31, 2018 at 2:50 PM eyal.yur...@gmail.com wrote: > Hi, > > I would look at data sketches as potentially a better alternative, with > the recent release of "Numeric quantiles sketch aggregator" (As noted in > the release notes: > https://github.com/apache/incubator-druid/releases/druid-0.12.0). > > Unfortunately, the documentation wasn't ready with that release, thus is > not available on the public website yet. It is marked to be released on the > next major milestone (0.13.0) and viable on the Druid master branch: > https://github.com/apache/incubator-druid/blob/master/docs/content/development/extensions-core/datasketches-quantiles.md > > > On 2018/08/31 10:13:56, Abhishek Kaushik wrote: > > Hi, > > > > I wanted to know which algorithm/s druid uses to compute percentile > values. > > I came across this doc: > > > http://druid.io/docs/latest/development/extensions-core/approximate-histograms.html > > but it mentions that there are "no formal error bounds on the > > approximation". So, just want to know what all options are available if > one > > wishes to compute percentiles? > > > > Thanks in advance. > > > > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
Podling Report Reminder - September 2018
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 September 2018, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, September 05). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/September2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Towards 0.13 (Apache release)
Hi, my only issue that GitHub loses the commit history beyond the rename (i.e.: https://github.com/apache/incubator-druid/blob/master/server/src/main/java/org/apache/druid/server/ClientQuerySegmentWalker.java). Luckily it is viewable locally via "git log --follow" or with using your favorite SCM GUI tool. On 2018/08/29 16:34:52, Gian Merlino wrote: > Hi everyone, > > As we continue towards 0.13 I started looking into the "great renaming" (of > all packages from io.druid -> org.apache.druid) and am getting a PR ready. > I know Slim is working on > https://github.com/apache/incubator-druid/pull/6215 too (automated license > checking and some header fixups). > > Other than these Apache related items, we have 26 open issues/PRs in the > 0.13.0 milestone: https://github.com/apache/incubator-druid/milestone/25. > Is this everything we want to include? Is anything there we should bump to > the next release? Is anything _not_ there that needs to be added? > > Let's figure out when we can target a code freeze -- the start of the RC > train for our first Apache release!! > - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
