Yup we can certainly include it if RC0 fails. So far I’m inclined to not
consider it a blocker. I’ve requested Vova and Anton to take a look.
So folks, please continue to test the candidate.
On Sun, Aug 30, 2020 at 6:16 PM Charles Givre wrote:
> Ok. Are you looking to include DRILL-7785? I
Ok. Are you looking to include DRILL-7785? I don't think it's a blocker, but
if we find anything with RC0... let's make sure we get it in.
-- C
> On Aug 30, 2020, at 9:14 PM, Abhishek Girish wrote:
>
> Hey Charles,
>
> I would have liked to. We did get one of the PRs merged after the
Hey Charles,
I would have liked to. We did get one of the PRs merged after the master
branch was closed as I hadn't made enough progress with the release yet.
But that’s not the case now.
Unless DRILL-7781 is a release blocker, we should probably skip it. So far,
a lot of effort has gone into
HI Abhishek,
Can we merge DRILL-7781? We really shouldn't ship something with a simple bug
like this.
-- C
> On Aug 30, 2020, at 8:40 PM, Abhishek Girish wrote:
>
> Advanced tests from [5] are also complete. All 7500+ tests passed, except
> for a few relating to known resource issues
Advanced tests from [5] are also complete. All 7500+ tests passed, except
for a few relating to known resource issues (drillbit connectivity / OOM
/...). Plus a few with the same symptoms as DRILL-7785.
On Sun, Aug 30, 2020 at 2:17 PM Abhishek Girish wrote:
> Wanted to share an update on some
Wanted to share an update on some of the testing I've done from my side:
All Functional tests from [5] (plus private Customer tests) are complete.
10,000+ tests have passed. However, I did see an issue with Hive ORC tables
(DRILL-7785). Need to investigate if it's a blocker for the release.
Of
Hi all,
I'd like to propose the first release candidate (RC0) of Apache Drill,
version 1.18.0.
The release candidate covers a total of 164 resolved JIRAs [1]. Thanks to
everyone who contributed to this release.
The tarball artifacts are hosted at [2] and the maven artifacts are hosted
at [3].
