> > Peter
> >
> > > On Jan 17, 2018, at 12:40 AM, Vihang Karajgaonkar <vih...@cloudera.com
> >
> > wrote:
> > >
> > > Thanks for the headsup Alan. I am okay with the rebasing
> > > standalone-metastore branch. Will update my WIP
; > Thanks for the headsup Alan. I am okay with the rebasing
> > standalone-metastore branch. Will update my WIP patches accordingly.
> >
> > On Tue, Jan 16, 2018 at 2:01 PM, Alan Gates <alanfga...@gmail.com>
> wrote:
> >
> >> I’ve committed HIVE-17982 to
Thanks Alan!
Go on with the rebase.
Peter
> On Jan 17, 2018, at 12:40 AM, Vihang Karajgaonkar <vih...@cloudera.com> wrote:
>
> Thanks for the headsup Alan. I am okay with the rebasing
> standalone-metastore branch. Will update my WIP patches accordingly.
>
> On Tue,
Thanks for the headsup Alan. I am okay with the rebasing
standalone-metastore branch. Will update my WIP patches accordingly.
On Tue, Jan 16, 2018 at 2:01 PM, Alan Gates <alanfga...@gmail.com> wrote:
> I’ve committed HIVE-17982 to master. I have been rebasing
> standalone-metastor
I’ve committed HIVE-17982 to master. I have been rebasing
standalone-metastore after each push of a patch from it to master to keep
it close to master. Vihang and maybe Peter have patches against it, so
this will bust your history. It will force you to rebase your branches
when you fetch from
I have committed HIVE-17981 to master and will be rebasing the
standalone-metastore up to the current master branch.
Alan.
As HIVE-17980 has been committed to master, I will be rebasing the
standalone-metastore branch up to the latest in master. This will again be
a force push.
In this rebase I am also including a newer version of HIVE-17983, which
includes integration tests that use docker images to test the
I'm about to check in HIVE-17967. Once I do that, I will rebase the
standalone-metastore branch onto master post that commit and then force
push it. This way the branch will be up to date with master again.
Alan.
