Return-Path: X-Original-To: apmail-drill-dev-archive@www.apache.org Delivered-To: apmail-drill-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D72A18A97 for ; Mon, 4 Jan 2016 21:59:35 +0000 (UTC) Received: (qmail 34650 invoked by uid 500); 4 Jan 2016 21:59:34 -0000 Delivered-To: apmail-drill-dev-archive@drill.apache.org Received: (qmail 34597 invoked by uid 500); 4 Jan 2016 21:59:34 -0000 Mailing-List: contact dev-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list dev@drill.apache.org Received: (qmail 34582 invoked by uid 99); 4 Jan 2016 21:59:34 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 21:59:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E640EC0752 for ; Mon, 4 Jan 2016 21:59:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=maprtech.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LbWT01B9zQ6y for ; Mon, 4 Jan 2016 21:59:27 +0000 (UTC) Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id D8C1F20FF3 for ; Mon, 4 Jan 2016 21:59:26 +0000 (UTC) Received: by mail-wm0-f47.google.com with SMTP id f206so2608428wmf.0 for ; Mon, 04 Jan 2016 13:59:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maprtech.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=OewWX0sotVfYupyFPv+NI9zMfTlE9pmYf9TunLZ4D+c=; b=CaJyStxhtKErxwBKD/iqyzs/ACEcdmBn3UwF3q67VV2vHBymgtIcdhKTLlFv9FgsqC BLu5Liq58UuYirL9DUdXEYzjZl2GOlTF7JRF3Q6lnYWJprnd9S4fJuVr+HLE04hPq58I fqgKikNLHmYuuCU0Yit1YKme0PezzXIuE9ohc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=OewWX0sotVfYupyFPv+NI9zMfTlE9pmYf9TunLZ4D+c=; b=QqtwMC+Fi5yAQOvUyp9o+SuEEdq0to5S82iy9sl0K57xMZsI1tjfyR8cNXUP/IY6x2 qg8Ji/24sL6WE1vgnBfRKWOHtAk2wXGKhUWWaTYxO5331DymzXRiuPhSsNgMkaKmLEHu 6nsa3DK4tOfCXF4w9e95Um9/CbdMulSad1OfTUU7agGPC0pLD4BZLYLznis+e48lG6ps 0LNsfrdjvbZB2wZh+w5yRJOuD84tBpmchjbN7Sa+Vmes2+3g97CPYFGIlqfwnFzuaFXI f4SCMGtvYomOD5ItQ+CMDnP8n3MpeWqw6ffHAIEOuYvYdJkSQhEx6bLZ11cXChHmwveN Pc9Q== X-Gm-Message-State: ALoCoQl54isa3JyXdfQ45tHC1GbMXmxI1dLjSPx/nOmWNhDcfOy+hWMMzkHptDtwP1LmEqWrOZYidg/OH8iplORNY3ACu+CcotfrRYkc8VAOgjRCyOUhV9I= MIME-Version: 1.0 X-Received: by 10.194.6.196 with SMTP id d4mr97891936wja.120.1451944759166; Mon, 04 Jan 2016 13:59:19 -0800 (PST) Received: by 10.28.102.86 with HTTP; Mon, 4 Jan 2016 13:59:19 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Jan 2016 13:59:19 -0800 Message-ID: Subject: Re: Time for a 1.5 release? From: Abdel Hakim Deneche To: "dev@drill.apache.org" Content-Type: multipart/alternative; boundary=047d7b5d49769aba7c0528893b04 --047d7b5d49769aba7c0528893b04 Content-Type: text/plain; charset=UTF-8 We are seeing an IllegalStateException in one of functional tests (flatten), I already reported it in DRILL-4246, I think this should be fixed as part of 1.5 release [1] [1] https://issues.apache.org/jira/browse/DRILL-4246 On Mon, Jan 4, 2016 at 1:52 PM, Amit Hadke wrote: > https://issues.apache.org/jira/browse/DRILL-4190 > https://issues.apache.org/jira/browse/DRILL-4196 > > I'm working on a fix for both of these. > > On Mon, Jan 4, 2016 at 1:48 PM, Jason Altekruse > wrote: > > > Hello All, > > > > With the allocator changes merged and about a month since the last > release > > I think it would be good to start a vote soon. I would like to volunteer > to > > be release manager. > > > > I know that there were some issues that were identified after the > transfer > > patch was merged. I think that these issues should be fixed before we > cut a > > release candidate. > > > > From looking at the associated JIRAs it looked like there was a possible > > short term fix just adjusting the max_query_memory_per_node option, and > > some more involved work to change how we determine the correct time to > > spill during external sort. I believe it makes sense to make external > sort > > work well with the newly improved memory accounting before cutting a > > release, but I'm not sure how much work is left to be done there. [1] > > > > Please respond with your thoughts on a release soon and any JIRAs you > would > > like to include in the release. > > > > [1] - https://issues.apache.org/jira/browse/DRILL-4243 > > > > Thanks, > > Jason > > > -- Abdelhakim Deneche Software Engineer Now Available - Free Hadoop On-Demand Training --047d7b5d49769aba7c0528893b04--