Re: splitPoint parameter in splitRegionAsync

ok, I got you Thanks stack. Stack 於 2019年3月29日 週五 上午5:45寫道： > The end key of one region is the start key of the next so cecking the > startkey is sufficient? > Thanks Kevin, > S > > > On Tue, Mar 26, 2019 at 1:47 PM kevin su wrote: > > > Hi Users, > > > > I found that when we start to split

Re: splitPoint parameter in splitRegionAsync

The end key of one region is the start key of the next so cecking the startkey is sufficient? Thanks Kevin, S On Tue, Mar 26, 2019 at 1:47 PM kevin su wrote: > Hi Users, > > I found that when we start to split region, used splitRegionAsync in > HbaseAdmin. > it only check whether the

Re: splitPoint parameter in splitRegionAsync

hi stack, In the hbase/client/HBaseAdmin.java : https://goo.gl/hojSM3 Future splitRegionAsync(RegionInfo hri, byte[] splitPoint) throws IOException { TableName tableName = hri.getTable(); if (hri.getStartKey() != null && splitPoint != null &&

Re: splitPoint parameter in splitRegionAsync

That sounds right Kevin. Mind adding pointer to where in the code you are referring to? Thanks, S On Tue, Mar 26, 2019 at 1:47 PM kevin su wrote: > Hi Users, > > I found that when we start to split region, used splitRegionAsync in > HbaseAdmin. > it only check whether the splitPoint is startkey

splitPoint parameter in splitRegionAsync

Hi Users, I found that when we start to split region, used splitRegionAsync in HbaseAdmin. it only check whether the splitPoint is startkey or not. should we also check splitPoint is endkey ? Thanks. Kevin