Yes. I removed one. Let me check.

--Xuefu


On Sat, Mar 15, 2014 at 4:04 PM, Brock Noland <[email protected]> wrote:

> That change was two commits: https://github.com/apache/hive/commits/trunk
>
> I guess only one of them was reverted?
>
>
> On Sat, Mar 15, 2014 at 5:37 PM, Xuefu Zhang <[email protected]> wrote:
>
> > Even after the reversion, the build is still failing. Anyone has any
> idea?
> >
> >
> > On Sat, Mar 15, 2014 at 2:07 PM, Xuefu Zhang <[email protected]>
> wrote:
> >
> > > The commit made via HIVE-6432 was reverted to make the precommit test
> > > going. The JIRA was reopened.
> > >
> > > Thanks, guys!
> > >
> > > --Xuefu
> > >
> > >
> > > On Sat, Mar 15, 2014 at 1:42 PM, Szehon <[email protected]> wrote:
> > >
> > >> Hi I dont think so yet, the change needs to be reverted or packaging
> pom
> > >> fixed.
> > >>
> > >> Thanks
> > >> Szehon
> > >>
> > >> Sent from my iPhone
> > >>
> > >> On Mar 15, 2014, at 12:23 PM, Prasanth Jayachandran <
> > >> [email protected]> wrote:
> > >>
> > >> > Is the precommit build error fixed now?
> > >> >
> > >> > Thanks
> > >> > Prasanth
> > >> > Sent from my iPhone
> > >> >
> > >> >> On Mar 15, 2014, at 10:57 AM, Szehon Ho <[email protected]>
> wrote:
> > >> >>
> > >> >> Hi,
> > >> >>
> > >> >> I saw all pre-commit builds in queue have build failure, it seems
> due
> > >> to
> > >> >> recent change of removing hcatalog hbase storage handler.
> > >> >>
> > >> >> If there was a pending patch, it needs to be resubmitted again once
> > the
> > >> >> branch is fixed.
> > >> >>
> > >> >> Thanks
> > >> >> Szehon
> > >> >
> > >> > --
> > >> > CONFIDENTIALITY NOTICE
> > >> > NOTICE: This message is intended for the use of the individual or
> > >> entity to
> > >> > which it is addressed and may contain information that is
> > confidential,
> > >> > privileged and exempt from disclosure under applicable law. If the
> > >> reader
> > >> > of this message is not the intended recipient, you are hereby
> notified
> > >> that
> > >> > any printing, copying, dissemination, distribution, disclosure or
> > >> > forwarding of this communication is strictly prohibited. If you have
> > >> > received this communication in error, please contact the sender
> > >> immediately
> > >> > and delete it from your system. Thank You.
> > >>
> > >
> > >
> >
>

Reply via email to