Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Received-SPF: pass (nike.apache.org: domain of brock@cloudera.com designates
 209.85.215.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <0B925182-D07E-4822-B4EB-2554C0DA6793@sourcethought.com>
References: <0B925182-D07E-4822-B4EB-2554C0DA6793@sourcethought.com>
From: Brock Noland <brock@cloudera.com>
Date: Wed, 4 Sep 2013 07:42:10 -0500
Message-ID: 
 <CAFukC=5zNcaN8M3wEYPxdcVuwXVqQpaGVe4gQf5u9ydsbUt_NA@mail.gmail.com>
Subject: Re: HIVE-5104 patch status?
To: dev@hive.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Looks like your patch has been committed, but I just wanted to confirm
for those lurking. If you have a patch up on a JIRA, emailing the dev
list is one of the correct ways of engaging a committer. IRC is also a
viable strategy.

Thanks for your contribution!!

Cheers,
Brock

On Tue, Sep 3, 2013 at 1:59 PM, Karl Gierach <karl@sourcethought.com> wrote:
> Hi,
>
> We at Sourcethought have contributed at patch to fix JIRA issue HIVE-5104 about 2 weeks back, although it appears that this patch has not received any comments.
>
> The patch is relevant for the both github Hive branch-0.11 and the trunk, as both source files were not changed since the 0.11 branch was created.
>
> What steps need to be taken to incorporate this patch into the next release?  Do we need to request approval from a committer?
>
> Best Regards,
>
> Karl Gierach
> Lead Engineer
> SourceThought, Inc.


-- 
Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org