Re: ingestion time aggregation in KIS broken in 0.15.1

to two separate Kafka tasks (or even the same task across a segment > boundary based on max row count or intermediate handoff). > > On Fri, Aug 9, 2019 at 10:50 AM Prashant Deva > wrote: > > > In this case there is only a single Kafka partition and rows are coming > in >

Re: ingestion time aggregation in KIS broken in 0.15.1

what partitions they come in from). But > nevertheless we'll check out this issue to see if it looks like something > is wrong. > > On Fri, Aug 9, 2019 at 9:57 AM Prashant Deva > wrote: > > > by ' Data sources that dont aggregate' i mean data sources that have same > &

Re: ingestion time aggregation in KIS broken in 0.15.1

by ' Data sources that dont aggregate' i mean data sources that have same query granularity as the data that is generated. Prashant On Fri, Aug 9, 2019 at 9:55 AM Prashant Deva wrote: > Only posting this because I think this is a major issue. > See bug #8276 <https:

ingestion time aggregation in KIS broken in 0.15.1

Only posting this because I think this is a major issue. See bug #8276 for details. Seems to be happening on every data source that is aggregating during ingestion. Data sources that dont aggregate dont have this issue. Prashant

Re: [VOTE] Release Apache Druid (incubating) 0.15.1 [RC2]

i think i ran into a pretty serious bug in 0.15.1... https://github.com/apache/incubator-druid/issues/8276 Prashant On Tue, Aug 6, 2019 at 3:04 PM Xavier Léauté wrote: > Yes, probably not a discussion for a voting thread, but I'm happy to look > into getting official docker images shipped. I k

Re: 0.15.1 and 0.16.0

i wonder if rolling upgrading from 0.15.0 to 0.15.1 should first update coordinator before other nodes. if not, then you will run into 8137 during the upgrade. Prashant On Wed, Jul 24, 2019 at 12:04 PM Jihoon Son wrote: > +1 for 0.15.1 > > The list of PRs looks good to me. > Thank you for volu

Re: Stalebot for issues

ill relevant, > otherwise they would be likely to sit open forever with nobody reviewing > them. > > On Thu, Jul 4, 2019 at 9:06 PM Prashant Deva > wrote: > > > stalebot just closed my issues 7473 and 7521. > > > > Both bugs are still present. > > > > they w

Re: Stalebot for issues

stalebot just closed my issues 7473 and 7521. Both bugs are still present. they were closed because the bug reports themselves didn’t receive a reply. Not receiving a reply did not make the bugs go away. Yet due to stalebot, the bugs are now closed. On Wed, Jun 26, 2019 at 10:28 AM Roman Levent

druid 0.12.3 rc

is it time to do an rc now since the milestone seems to be complete on github? Prashant

Re: KIS 100% broken in 0.12.2

update, > but the supervisor should re-spawn new tasks for the same startOffset of > the failed ones. > > What do you mean by 'fail irrecoverably'? > > Jihoon > > On Mon, Aug 13, 2018 at 3:25 PM Prashant Deva > wrote: > > > bug #6163 has completely b

KIS 100% broken in 0.12.2

bug #6163 has completely broken KIS in 0.12.2. All tasks will run into it and fail irrecoverably. I propose doing some sort of a nightly build with #6163 fix so folks affected can atleast get their clusters back up and running. Prashant

Re: Druid 0.12.2 release vote

Charles, did you post a screenshot? i cant see it.. Prashant On Thu, Aug 9, 2018 at 4:23 PM Jihoon Son wrote: > Hi all, thank you for the vote! > > The vote has passed with 8 positive votes (+1). > > I'm going to release 0.12.2. > > Best, > Jihoon > > On Thu, Aug 9, 2018 at 10:40 AM Charles A

Re: About creating 0.12.2-rc1

+1 Prashant On Fri, Aug 3, 2018 at 7:11 PM Niketh Sabbineni wrote: > +1 > > Looking forward to this > > On Fri, Aug 3, 2018 at 7:09 PM Jihoon Son wrote: > > > Hi folks, > > > > Releasing 0.12.2 has been delayed because, fortunately, we could find > more > > bugs to be fixed before release. > >

list polluted by gitbox messages

seems like every bit of activity on gitbox is being posted to the dev mailing list. its impossible to see any real messages since all i see are gitbox mails. Prashant

Re: Considering 0.12.2 release

://github.com/druid-io/druid/issues/5900) > > > > I'm currently working on https://github.com/druid-io/druid/issues/5729 > and > > https://github.com/druid-io/druid/issues/5745, and PRs will be ready in > > this week. > > > > What do you guys think about inclu

Re: Considering 0.12.2 release

aSegmentManager. > > > https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher: > > Close > > > tmpIndexFile before copying it. > > > > > > On Tue, Jun 12, 2018 at 11:34 AM Prashant Deva < > prashant.d...@gmail.com> > > > wrote: >

Re: Considering 0.12.2 release

+1 On Fri, Jun 8, 2018 at 3:37 PM Jihoon Son wrote: > Hi guys, > > we have a couple of bug fix PRs available and some of them fix regression > bugs. > > Here is the list of currently available bug fix PRs which are not included > in 0.12.1. > > Regression bug fixes > - https://github.com/druid-i

Re: Druid 0.12.1 release vote

guys is there more votes needed to do the release? On Wed, May 30, 2018 at 2:31 PM Prashant Deva wrote: > +1 to Gian's reply. I think some process overall to release minor versions > faster would be very beneficial. > > Prashant > > > On Wed, May 30, 2018 at 1:26 PM Gi

Re: Druid 0.12.1 release vote

ty major bug when the conditions that > > cause it are met. Sorry for being at the tail end of the vote, just found > > the issue last night. > > > > On Tue, May 29, 2018 at 3:45 PM, Jihoon Son > wrote: > > > > > +1 > > > > > > On Tue, M

Re: Druid 0.12.1 release vote

+1 Prashant On Tue, May 29, 2018 at 1:22 PM Gian Merlino wrote: > +1 > > On Tue, May 29, 2018 at 11:02 AM, Jonathan Wei wrote: > > > As discussed on the sync up call this morning, let's vote on the 0.12.1 > > release. > > > > Thanks, > > Jon > > > >

Re: Druid 0.12.1-rc2 vote

+1 On Mon, May 14, 2018 at 12:58 PM Jihoon Son wrote: > Hi all, > > we have no remaining issues ( > > https://github.com/druid-io/druid/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+0.12.1 > ) > or PRs ( > > https://github.com/druid-io/druid/pulls?q=is%3Aopen+is%3Apr+milestone%3A0.12.1 > ) > for

Re: Druid 0.12.1-rc1 vote

+1 On Tue, May 1, 2018 at 11:32 AM David Lim wrote: > +1 > > On Tue, May 1, 2018 at 12:11 PM, Jihoon Son wrote: > > > Gian, thanks. > > > > I posted on the old thread ( > > https://lists.apache.org/thread.html/7ebdca7e22da0ac097bf637 > > 7ffbe740b180f6cff203228c11b6e5e5c@%3Cdev.druid.apache.org

Re: Druid 0.12.1-rc1 vote

+1 Prashant On Wed, Apr 25, 2018 at 3:24 PM, Gian Merlino wrote: > +1 on doing 0.12.1-rc1. > > On Tue, Apr 24, 2018 at 2:59 PM, Jihoon Son wrote: > > > Thanks Julian, I forgot to mention that. > > > > Jihoon > > > > 2018년 4월 24일 (화) 오후 2:58, Julian Hyde 님이 작성: > > > > > You should make it clea

Re: [druid-dev] consider doing a 0.12.1 release

if nobody else gets to them. > > Nishant, I added https://github.com/druid-io/druid/pull/5596 to the > milestone. > > Prashant, I added https://github.com/druid-io/druid/pull/5611 to the > milestone. > > On Mon, Apr 9, 2018 at 1:10 PM, Prashant Deva > wrote: > >

Re: [druid-dev] consider doing a 0.12.1 release

> >> (#5316) > >> - SQL: Throttle metadata refreshes when they fail. (#5328) > >> > >> On Mon, Apr 9, 2018 at 10:35 AM, Gian Merlino wrote: > >> > >> I think this conversation is worth having. I have cross posted this to > >> dev@druid

Re: [druid-dev] consider doing a 0.12.1 release

; the dev list, please cross post any dev messages there, or even only post > > to that list. > > > > Gian > > > > On Sun, Apr 8, 2018 at 5:45 PM, Prashant Deva > > wrote: > > > >> Current 0.12.0 release has some major issues: > >> > &g