Hello,
branch-3 is now closed for commits. If you have anything you wanted to go in
3.0 please defer it to next release. I am working on stabilizing and preparing
RC.
Thanks,
Vineet Garg
> On May 7, 2018, at 11:34 AM, Vineet Garg wrote:
>
> Hello all,
>
> It’s been more than a month since
Owen, thanks for bringing this to attention. It is definitely me who made those
changes.
The good thing is the change is backward compatible and the new API is needed
to keep Vectorized mode performant while using Murmur hash.
We can treat this as a bug fix and I can work on a new point-point rel
Okay. Thanks for that information.
On Mon, May 7, 2018 at 12:45 PM, Thejas Nair wrote:
> Hi Vihang,
> That is expected if you have 2.4.0 release that happens little after
> (or around same time as) a 3.0 release.
> This is more likely to happen with last minute bug fixes.
>
>
>
> On Mon, May 7,
*Sigh* It looks like branch-3 requires features in storage-api that were
added after storage-api 2.6.0.
You'll need to make another storage-api release or revert those changes.
.. Owen
On Mon, May 7, 2018 at 11:58 AM, Vihang Karajgaonkar
wrote:
> How do we handle the cases where a patch needs
Hi Vihang,
That is expected if you have 2.4.0 release that happens little after
(or around same time as) a 3.0 release.
This is more likely to happen with last minute bug fixes.
On Mon, May 7, 2018 at 11:58 AM, Vihang Karajgaonkar
wrote:
> How do we handle the cases where a patch needs to go i
How do we handle the cases where a patch needs to go in branch-2? I think
the reason of the commits are going in branch-3 is because you don't want
have a intermediate version where a patch is missing. Eg: patch is fixed in
Hive 2.4.0 and Hive 3.1.0 but not Hive 3.0.0. Is that normal?
On Mon, May
Hello all,
It’s been more than a month since we have cutoff branch-3. There are tests
which are still failing
consistently(https://issues.apache.org/jira/browse/HIVE-19142). At this point
we should work on fixing tests and stabilize the branch. So please refrain from
committing anything but t
Thanks Vihang!
> On Apr 13, 2018, at 12:36 PM, Vihang Karajgaonkar wrote:
>
> Hi Vineet,
>
> I created a profile on ptest-server so that tests can be run on branch-3.
> It is the same as branch-2 patches. You will need to include branch-3 in
> the patch name. Eg. HIVE-1234.01-branch-3.patch
>
Hi Vineet,
I created a profile on ptest-server so that tests can be run on branch-3.
It is the same as branch-2 patches. You will need to include branch-3 in
the patch name. Eg. HIVE-1234.01-branch-3.patch
-Vihang
On Mon, Apr 9, 2018 at 4:35 PM, Vineet Garg wrote:
> I have created an umbrell
I have created an umbrella jira to investigate and fix test failures for hive
3.0.0. LINK : https://issues.apache.org/jira/browse/HIVE-19142.
Please link any other existing jira related to test failure with this umbrella
jira.
Also, how do we run tests on branch-3? Is there some setup to be done
Hello
A few weeks earlier I've tried to hunt down this problem...
so...to my best knowledge the cause of this seems to be the following:
* in some cases the "cleanup" after a failed query may somehow leave some
threads behind...
* these threads have reference to the "customized" session classloa
We need to investigate and find out root cause of these failures. If its
determined that its a corner case and fix is non-trivial then we may
release note it under known issues. But ideally we should fix these
failures.
Cutting a branch should make it easier since branch is expected to receive
lot
Cutting the branch before the tests are stabilized would mean we have to fix
them in 2 places.
On 4/6/18, 10:05 AM, "Thejas Nair" wrote:
That needs to be cleaned up. There are far too many right now, its
just not handful of flaky tests.
On Fri, Apr 6, 2018 at 2:48 AM, Pete
That needs to be cleaned up. There are far too many right now, its
just not handful of flaky tests.
On Fri, Apr 6, 2018 at 2:48 AM, Peter Vary wrote:
> Hi Team,
>
> I am new to the Hive release process and it is not clear to me how the
> failing tests are handled. Do we plan to fix the failing
Hi Team,
I am new to the Hive release process and it is not clear to me how the failing
tests are handled. Do we plan to fix the failing tests before release? Or it is
accepted to cut a new major release with known test issues.
Thanks,
Peter
> On Apr 5, 2018, at 8:25 PM, Vineet Garg wrote:
>
Hello,
I plan to cut off branch for Hive 3.0.0 on Monday (9 April) since bunch of
folks have big patches pending.
Regards,
Vineet G
> On Apr 2, 2018, at 3:14 PM, Vineet Garg wrote:
>
> Hello,
>
> We have enough votes to prepare a release candidate for Hive 3.0.0. I am
> going to cutoff a br
Hello,
We have enough votes to prepare a release candidate for Hive 3.0.0. I am going
to cutoff a branch in a day or two. I’ll send an email as soon as I have the
branch ready.
Meanwhile there are approximately 69 JIRAs which are currently opened with fix
version 3.0.0. I’ll appreciate if their
17 matches
Mail list logo
