+1 for hbase-native-client repo.
You can create a new gitbox repository on https://gitbox.apache.org/ by
filling out a simple form.

On Wed, Mar 20, 2019 at 8:48 AM Guanghao Zhang <zghao...@gmail.com> wrote:

> I am +1 to push the hbase-native-client to a new git repo. One more
> question, how to create a new repo in gitbox? Do we have some ref guide for
> this? Thanks.
>
> Sean Busbey <bus...@apache.org> 于2019年3月14日周四 下午9:58写道:
>
> > I'd also like to see the native client in its own repo. Dealing with a
> > new build system for C++ will be some overhead, but I suspect less
> > overhead than if we have to stitch that build to work with maven in
> > the same repo.
> >
> > Also I think the hbase-connectors repo is overdue for a release and
> > I'd rather avoid either rushing the C++ client, blocking to wait for
> > it, or doing the work to pull it aside when doing a release.
> >
> > On Thu, Mar 14, 2019 at 8:28 AM 张铎(Duo Zhang) <palomino...@gmail.com>
> > wrote:
> > >
> > > For hbase-connectors, it is still a maven project, but the native
> client
> > is
> > > a C++ project, so maybe we could just give it a separated repo...
> > >
> > > Stack <st...@duboce.net> 于2019年3月14日周四 下午1:54写道:
> > >
> > > > On Wed, Mar 13, 2019 at 12:54 AM Guanghao Zhang <zghao...@gmail.com>
> > > > wrote:
> > > > ...
> > > >
> > > > > As we have hbase-connectors project now and Sean Busbey suggested
> to
> > move
> > > > > the native client to hbase-connector project. Or we can create a
> new
> > > > > project hbase-native-client for this. But the problem is the
> > > > compatibility
> > > > > may be break when there are some changes in HBase project. Looking
> > > > forward
> > > > > to your suggestions.
> > > > >
> > > >
> > > > Would hbase-native-client be in hbase-connectors? I'd imagine this
> > would
> > > > make the development easier.
> > > >
> > > > Once you'd made a release of the new client, could we a step to the
> > nightly
> > > > build that pulls the new client and runs it through paces complaining
> > if it
> > > > fails?
> > > >
> > > > (sounds great)
> > > > S
> > > >
> >
>

Reply via email to