drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jinfeng Ni <jinfengn...@gmail.com>
Subject Re: Time for a 1.5 release?
Date Wed, 20 Jan 2016 15:57:01 GMT
I still saw mvn full build failed on linux due to the following unit
test case sometime:

Tests in error:
  TestTopNSchemaChanges.testMissingColumn:206 ยป  at position 0 column
'`kl1`' mi...

Either we comment out that unit test, or we should fix the test case.
Otherwise, people may see maven build failure from the 1.5.0 release.

On Tue, Jan 19, 2016 at 4:18 PM, Jacques Nadeau <jacques@dremio.com> wrote:
> Bumping this thread...
> Here are the issues that were mentioned in this thread along with a
> proposed categorization:
> Release Blockers
> In-progress Amit https://issues.apache.org/jira/browse/DRILL-4190
> In-progress Amit https://issues.apache.org/jira/browse/DRILL-4196
> Ready to merge Jacques https://issues.apache.org/jira/browse/DRILL-4246
> In-review Jinfeng https://issues.apache.org/jira/browse/DRILL-4256
> In-progress Jacques https://issues.apache.org/jira/browse/DRILL-4278
> Ready to merge Laurent https://issues.apache.org/jira/browse/DRILL-4285
> Nice to Have
> Open Jason/Hakim https://issues.apache.org/jira/browse/DRILL-4247
> In-progress Jason https://issues.apache.org/jira/browse/DRILL-4203
> Open Jacques https://issues.apache.org/jira/browse/DRILL-4266
> Ready to merge Jacques https://issues.apache.org/jira/browse/DRILL-4131
> What do others think? Let's try to get the blockers wrapped up in the next
> day or two and start a release vote...
> --
> Jacques Nadeau
> CTO and Co-Founder, Dremio
> On Mon, Jan 4, 2016 at 1:48 PM, Jason Altekruse <altekrusejason@gmail.com>
> 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

View raw message