What about https://issues.apache.org/jira/browse/DRILL-4247 and https://issues.apache.org/jira/browse/DRILL-4256? 4256 appears to be a regression. Not sure about 4247.
-- Zelaine On Tue, Jan 5, 2016 at 12:20 PM, Kristine Hahn <[email protected]> wrote: > https://issues.apache.org/jira/browse/DRILL-4239 (Drill reported not to > work on 32-bit Windows) has been opened as a doc bug, but maybe we're > actually talking about a product bug. If so, how about a fix in 1.5? > > Kristine Hahn > Sr. Technical Writer > 415-497-8107 @krishahn skype:krishahn > > > On Mon, Jan 4, 2016 at 1:48 PM, Jason Altekruse <[email protected]> > 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 > > >
