; > > objection.
> > > Thanks,
> > > S
> > >
> > > On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I've had the opportunity to talk about HBCK2 with a f
> > On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> > wrote:
> > >
> > > Hi,
> > >
> > > I've had the opportunity to talk about HBCK2 with a few of you. One of
> > the
> > > suggestions is to to have a separate git repository for HBCK2. Lets
> >
with a few of you. One of the
> suggestions is to to have a separate git repository for HBCK2. Lets discuss
> about it.
>
> In the past when bugs were found in hbck, there is no easy way to release
> patched version of just hbck (without patching HBase). If HBCK2 has a
> separate git
> allow these in new minors, so we could potentially move hbck out in a
> > > 1.5.0.
> > >
> > >
> > > On Mon, Jul 23, 2018 at 4:46 PM Stack wrote:
> > >
> > > > On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> > >
rote:
> > >
> > > > Hi,
> > > >
> > > > I've had the opportunity to talk about HBCK2 with a few of you. One
> of
> > > the
> > > > suggestions is to to have a separate git repository for HBCK2. Lets
> > > discu
ck wrote:
>
> > On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> > >
> > wrote:
> >
> > > Hi,
> > >
> > > I've had the opportunity to talk about HBCK2 with a few of you. One of
> > the
> > > suggestions is to to have a separa
g that this *is* a goal -- could/should we introduce
> some new level of InterfaceAudience to assert that we don't
> inadvertently break HBCK2?
>
> Thanks!
>
> On 7/19/18 5:09 PM, Umesh Agashe wrote:
> > Hi,
> >
> > I've had the opportunity to talk about HBCK
can
> >> allow these in new minors, so we could potentially move hbck out in a
> >> 1.5.0.
> >>
> >>
> >> On Mon, Jul 23, 2018 at 4:46 PM Stack wrote:
> >>
> >>> On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> >> >>>>
so we could potentially move hbck out in a
> >> 1.5.0.
> >>
> >>
> >> On Mon, Jul 23, 2018 at 4:46 PM Stack wrote:
> >>
> >>> On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
> >> >>>>
> >>> wrote:
> >>>
y compatibility. They only change
> >> the promises we make going forward about their stability. I believe we
> can
> >> allow these in new minors, so we could potentially move hbck out in a
> >> 1.5.0.
> >>
> >>
> >> On Mon, Jul 23, 2018 at 4:46 PM Stack wrote
talk about HBCK2 with a few of you. One of
the
suggestions is to to have a separate git repository for HBCK2. Lets
discuss
about it.
In the past when bugs were found in hbck, there is no easy way to
release
patched version of just hbck (without patching HBase). If HBCK2 has a
separate git r
gt; > >
> > > I've had the opportunity to talk about HBCK2 with a few of you. One of
> > the
> > > suggestions is to to have a separate git repository for HBCK2. Lets
> > discuss
> > > about it.
> > >
> > > In the past when bugs were found in hbck, there
, 2018 at 4:46 PM Stack wrote:
> On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe >
> wrote:
>
> > Hi,
> >
> > I've had the opportunity to talk about HBCK2 with a few of you. One of
> the
> > suggestions is to to have a separate git repository for HBCK2. Lets
>
of the
suggestions is to to have a separate git repository for HBCK2. Lets discuss
about it.
In the past when bugs were found in hbck, there is no easy way to release
patched version of just hbck (without patching HBase). If HBCK2 has a
separate git repo, HBCK2 versions will not be tightly related
On Thu, Jul 19, 2018 at 2:09 PM Umesh Agashe
wrote:
> Hi,
>
> I've had the opportunity to talk about HBCK2 with a few of you. One of the
> suggestions is to to have a separate git repository for HBCK2. Lets discuss
> about it.
>
> In the past when bugs were found in hbck,
Hi,
I've had the opportunity to talk about HBCK2 with a few of you. One of the
suggestions is to to have a separate git repository for HBCK2. Lets discuss
about it.
In the past when bugs were found in hbck, there is no easy way to release
patched version of just hbck (without patching HBase
16 matches
Mail list logo
