Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Yu Li]

HBASE-20188 is comparing latest 2.0 to our stable pointer 1.2.7, and there
seems to be no conclusion yet, JFYI. While yes I believe more numbers could
give us a broader view :-)

And I'm not sure but is performance regression some kind of a blocker for
the release? Thanks.

Best Regards,
Yu

On 11 April 2018 at 08:39, 张铎(Duo Zhang)  wrote:

> Do we have a ITBLL result and also some performance numbers? I could help
> getting some performance numbers comparing to the version we use...
>
> 2018-04-11 5:50 GMT+08:00 Sean Busbey :
>
> > no compat report in the RC directory. does that mean we won't have one
> > in the dist area?
> >
> >
> > not a blocker; we've been inconsistent on it in prior releases, but
> > the trend seemed to be towards including it.
> >
> >
> > On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > > The first release candidate for Apache HBase 2.0.0 is available for
> > > downloading and testing.
> > >
> > > Artifacts are available here:
> > >
> > >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> > >
> > > Maven artifacts are available in the staging repository at:
> > >
> > >  https://repository.apache.org/content/repositories/
> orgapachehbase-1209
> > >
> > > All artifacts are signed with my signing key 8ACC93D2, which is also
> > > in the project KEYS file at
> > >
> > >  http://www.apache.org/dist/hbase/KEYS
> > >
> > > These artifacts were tagged 2.0.0RC0 at
> > > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> > >
> > > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > > Reference Guide before installing or upgrading for a list of
> > > incompatibilities, major changes, and notable new features. Be aware
> that
> > > according to our adopted Semantic Versioning guidelines[1], we've allow
> > > ourselves to make breaking changes in this major version release. For
> > > example, Coprocessors will need to be recast to fit more constrained CP
> > > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> > > downtime is (currently) not possible. That said, a bunch of effort has
> > been
> > > expended mitigating differences; a hbase-1.x client can perform DML
> > against
> > > an hbase-2 cluster.
> > >
> > > For the full list of ~6k issues addressed, see [2]. There are also
> > > CHANGES.md and RELEASENOTES.md in the root directory of the source
> > tarball.
> > >
> > > Please take a few minutes to verify the release and vote on releasing
> it:
> > >
> > > [ ] +1 Release this package as Apache HBase 2.0.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > This VOTE will run for one week and close Tuesday, April 17, 2018 @
> 13:00
> > > PST.
> > >
> > > Thanks to the myriad who have helped out with this release,
> > > Your 2.0.0 Release Manager
> > >
> > > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > > 2.  https://s.apache.org/zwS9
> >
>

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Duo Zhang]

Do we have a ITBLL result and also some performance numbers? I could help
getting some performance numbers comparing to the version we use...

2018-04-11 5:50 GMT+08:00 Sean Busbey :

> no compat report in the RC directory. does that mean we won't have one
> in the dist area?
>
>
> not a blocker; we've been inconsistent on it in prior releases, but
> the trend seemed to be towards including it.
>
>
> On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> > The first release candidate for Apache HBase 2.0.0 is available for
> > downloading and testing.
> >
> > Artifacts are available here:
> >
> >  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
> >
> > Maven artifacts are available in the staging repository at:
> >
> >  https://repository.apache.org/content/repositories/orgapachehbase-1209
> >
> > All artifacts are signed with my signing key 8ACC93D2, which is also
> > in the project KEYS file at
> >
> >  http://www.apache.org/dist/hbase/KEYS
> >
> > These artifacts were tagged 2.0.0RC0 at
> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
> >
> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> > Reference Guide before installing or upgrading for a list of
> > incompatibilities, major changes, and notable new features. Be aware that
> > according to our adopted Semantic Versioning guidelines[1], we've allow
> > ourselves to make breaking changes in this major version release. For
> > example, Coprocessors will need to be recast to fit more constrained CP
> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> > downtime is (currently) not possible. That said, a bunch of effort has
> been
> > expended mitigating differences; a hbase-1.x client can perform DML
> against
> > an hbase-2 cluster.
> >
> > For the full list of ~6k issues addressed, see [2]. There are also
> > CHANGES.md and RELEASENOTES.md in the root directory of the source
> tarball.
> >
> > Please take a few minutes to verify the release and vote on releasing it:
> >
> > [ ] +1 Release this package as Apache HBase 2.0.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
> > PST.
> >
> > Thanks to the myriad who have helped out with this release,
> > Your 2.0.0 Release Manager
> >
> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> > 2.  https://s.apache.org/zwS9
>

[jira] [Resolved] (HBASE-20380) Put up 2.0.0RC0

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-20380.
---
Resolution: Fixed

> Put up 2.0.0RC0
> ---
>
> Key: HBASE-20380
> URL: https://issues.apache.org/jira/browse/HBASE-20380
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 2.0.0
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.0
>
>
> JIRA to hang 2.0.0RC0-making steps on.
> I ran the below out of yetus and copied over new CHANGELOG and RELEASENOTES 
> to what is in branch-2.0.
> {code}
> $ ./release-doc-maker/releasedocmaker.py -p HBASE --fileversions -v 2.0.0  -l 
> --sortorder=newer --skip-credits
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20385) Purge md5-making from our little make_rc.sh script

[stack (JIRA)]

stack created HBASE-20385:
-

 Summary: Purge md5-making from our little make_rc.sh script
 Key: HBASE-20385
 URL: https://issues.apache.org/jira/browse/HBASE-20385
 Project: HBase
  Issue Type: Bug
Reporter: stack


Don't generate md5s anymore. New Apache release policy via Apache 
Infrastructure asks that we not provide md5 as md5 is 'broken for many 
purposes; we should movea awy from it.' Remove the md5' making from our 
make-rc.sh script.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20384) [AMv2] Logging format improvements; use encoded name rather than full region name marking transitions

[stack (JIRA)]

stack created HBASE-20384:
-

 Summary: [AMv2] Logging format improvements; use encoded name 
rather than full region name marking  transitions
 Key: HBASE-20384
 URL: https://issues.apache.org/jira/browse/HBASE-20384
 Project: HBase
  Issue Type: Bug
Reporter: stack


We use encoded name near everywhere. Makes logging regular-looking at least and 
eases tracing. In a few places we still do full region name. Let me fix (ran 
into it trying to debug...)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20383) [AMv2] AssignmentManager: Failed transition XYZ is not OPEN

[stack (JIRA)]

stack created HBASE-20383:
-

 Summary: [AMv2] AssignmentManager: Failed transition XYZ is not 
OPEN
 Key: HBASE-20383
 URL: https://issues.apache.org/jira/browse/HBASE-20383
 Project: HBase
  Issue Type: Bug
Reporter: stack


Seeing a bunch of this testing 2.0.0:

{code}
2018-04-10 13:57:09,430 WARN  
[RpcServer.default.FPBQ.Fifo.handler=46,queue=1,port=16000] 
assignment.AssignmentManager: Failed transition 

  
org.apache.hadoop.hbase.client.DoNotRetryRegionException: 
19a2cd6f88abae0036415ee1ea041c2e is not OPEN
  at 
org.apache.hadoop.hbase.master.procedure.AbstractStateMachineTableProcedure.checkOnline(AbstractStateMachineTableProcedure.java:193)
  at 
org.apache.hadoop.hbase.master.assignment.SplitTableRegionProcedure.(SplitTableRegionProcedure.java:112)
  at 
org.apache.hadoop.hbase.master.assignment.AssignmentManager.createSplitProcedure(AssignmentManager.java:769)


 at 
org.apache.hadoop.hbase.master.assignment.AssignmentManager.updateRegionSplitTransition(AssignmentManager.java:911)


  at 
org.apache.hadoop.hbase.master.assignment.AssignmentManager.reportRegionStateTransition(AssignmentManager.java:819)
  at 
org.apache.hadoop.hbase.master.MasterRpcServices.reportRegionStateTransition(MasterRpcServices.java:1538)
  at 
org.apache.hadoop.hbase.shaded.protobuf.generated.RegionServerStatusProtos$RegionServerStatusService$2.callBlockingMethod(RegionServerStatusProtos.java:11093)
  at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:409)
  at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:130)
  at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:324)  


  at 
org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:304)
{code}

Looks like report back from Master OK'ing a split to go ahead but the split is 
already running. Figure how to shut these down. They are noisy at least.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20382) If RSGroups not enabled, rsgroup.jsp prints stack trace

[Mike Drob (JIRA)]

Mike Drob created HBASE-20382:
-

 Summary: If RSGroups not enabled, rsgroup.jsp prints stack trace
 Key: HBASE-20382
 URL: https://issues.apache.org/jira/browse/HBASE-20382
 Project: HBase
  Issue Type: Bug
  Components: rsgroup, UI
Reporter: Mike Drob
 Fix For: 2.0.0


Going to {{rsgroup.jsp?name=foo}} I get the following stack trace:

{noformat}
org.apache.hadoop.hbase.TableNotFoundException: hbase:rsgroup
at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegionInMeta(ConnectionImplementation.java:842)
at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:733)
at 
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:719)
at 
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at 
org.apache.hadoop.hbase.client.ConnectionImplementation.locateRegion(ConnectionImplementation.java:690)
at 
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.locateRegion(ConnectionUtils.java:131)
at 
org.apache.hadoop.hbase.client.ConnectionImplementation.getRegionLocation(ConnectionImplementation.java:571)
at 
org.apache.hadoop.hbase.client.ConnectionUtils$ShortCircuitingClusterConnection.getRegionLocation(ConnectionUtils.java:131)
at 
org.apache.hadoop.hbase.client.HRegionLocator.getRegionLocation(HRegionLocator.java:73)
at 
org.apache.hadoop.hbase.client.RegionServerCallable.prepare(RegionServerCallable.java:223)
at 
org.apache.hadoop.hbase.client.RpcRetryingCallerImpl.callWithRetries(RpcRetryingCallerImpl.java:105)
at org.apache.hadoop.hbase.client.HTable.get(HTable.java:385)
at org.apache.hadoop.hbase.client.HTable.get(HTable.java:359)
at 
org.apache.hadoop.hbase.RSGroupTableAccessor.getRSGroupInfo(RSGroupTableAccessor.java:75)
at 
org.apache.hadoop.hbase.generated.master.rsgroup_jsp._jspService(rsgroup_jsp.java:78)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:840)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1772)
at 
org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:112)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at 
org.apache.hadoop.hbase.http.ClickjackingPreventionFilter.doFilter(ClickjackingPreventionFilter.java:48)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at 
org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1374)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at 
org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at 
org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1759)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:582)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:512)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:534)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
at 

Re: [VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Sean Busbey]

no compat report in the RC directory. does that mean we won't have one
in the dist area?


not a blocker; we've been inconsistent on it in prior releases, but
the trend seemed to be towards including it.


On Tue, Apr 10, 2018 at 3:47 PM, Stack  wrote:
> The first release candidate for Apache HBase 2.0.0 is available for
> downloading and testing.
>
> Artifacts are available here:
>
>  https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/
>
> Maven artifacts are available in the staging repository at:
>
>  https://repository.apache.org/content/repositories/orgapachehbase-1209
>
> All artifacts are signed with my signing key 8ACC93D2, which is also
> in the project KEYS file at
>
>  http://www.apache.org/dist/hbase/KEYS
>
> These artifacts were tagged 2.0.0RC0 at
> hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46
>
> Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
> Reference Guide before installing or upgrading for a list of
> incompatibilities, major changes, and notable new features. Be aware that
> according to our adopted Semantic Versioning guidelines[1], we've allow
> ourselves to make breaking changes in this major version release. For
> example, Coprocessors will need to be recast to fit more constrained CP
> APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
> downtime is (currently) not possible. That said, a bunch of effort has been
> expended mitigating differences; a hbase-1.x client can perform DML against
> an hbase-2 cluster.
>
> For the full list of ~6k issues addressed, see [2]. There are also
> CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.
>
> Please take a few minutes to verify the release and vote on releasing it:
>
> [ ] +1 Release this package as Apache HBase 2.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
> PST.
>
> Thanks to the myriad who have helped out with this release,
> Your 2.0.0 Release Manager
>
> 1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
> 2.  https://s.apache.org/zwS9

[VOTE] First release candidate for HBase 2.0.0 (RC0) is available

[Stack]

The first release candidate for Apache HBase 2.0.0 is available for
downloading and testing.

Artifacts are available here:

 https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/

Maven artifacts are available in the staging repository at:

 https://repository.apache.org/content/repositories/orgapachehbase-1209

All artifacts are signed with my signing key 8ACC93D2, which is also
in the project KEYS file at

 http://www.apache.org/dist/hbase/KEYS

These artifacts were tagged 2.0.0RC0 at
hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46

Please review 'Upgrading from 1.x to 2.x' in the bundled HBase 2.0.0
Reference Guide before installing or upgrading for a list of
incompatibilities, major changes, and notable new features. Be aware that
according to our adopted Semantic Versioning guidelines[1], we've allow
ourselves to make breaking changes in this major version release. For
example, Coprocessors will need to be recast to fit more constrained CP
APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x without
downtime is (currently) not possible. That said, a bunch of effort has been
expended mitigating differences; a hbase-1.x client can perform DML against
an hbase-2 cluster.

For the full list of ~6k issues addressed, see [2]. There are also
CHANGES.md and RELEASENOTES.md in the root directory of the source tarball.

Please take a few minutes to verify the release and vote on releasing it:

[ ] +1 Release this package as Apache HBase 2.0.0
[ ] +0 no opinion
[ ] -1 Do not release this package because...

This VOTE will run for one week and close Tuesday, April 17, 2018 @ 13:00
PST.

Thanks to the myriad who have helped out with this release,
Your 2.0.0 Release Manager

1. http://hbase.apache.org/2.0/book.html#hbase.versioning.post10
2.  https://s.apache.org/zwS9

Re: [DISCUSS] RowCounter duplication

[Chia-Ping Tsai]

There are other tools having two versions - o.a.h.h.mapreduce and o.a.h.h.mapred
It seems to me the question is "should hbase support old MR APIs ?' Given that 
hadoop 3.0 doesn't mark old MR APIs deprecated, we should keep them in hbase? 
Or we can deprecate them in hbase-2+ in order to remove them in the future?

On 2018/04/10 16:02:07, Peter Somogyi  wrote: 
> Hi,
> 
> Currently we have 2 RowCounter tools in our
> repository: o.a.h.h.mapreduce.RowCounter and o.a.h.h.mapred.RowCounter.
> None of them is marked as deprecated but mapred.RowCounter was deprecated
> in pre-HBase 1 releases and the annotation was eventually removed
> in HBASE-11178.
> 
> Do we still want to or need to keep both versions? The mapred tool is not
> documented in refguide and the command's usage is minimal. The
> mapreduce.RowCounter tool also has more features.
> 
> Thanks,
> Peter
> 

[jira] [Created] (HBASE-20381) precommit failing w/rat on shadedjars plugin

[Sean Busbey (JIRA)]

Sean Busbey created HBASE-20381:
---

 Summary: precommit failing w/rat on shadedjars plugin
 Key: HBASE-20381
 URL: https://issues.apache.org/jira/browse/HBASE-20381
 Project: HBase
  Issue Type: Bug
  Components: test
Reporter: Sean Busbey
Assignee: Sean Busbey


see HBASE-20219 and related builds.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-20149) Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)

[stack (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack resolved HBASE-20149.
---
  Resolution: Fixed
Assignee: stack  (was: Artem Ervits)
Hadoop Flags: Reviewed

Resolving.

> Purge dev javadoc from bin tarball (or make a separate tarball of javadoc)
> --
>
> Key: HBASE-20149
> URL: https://issues.apache.org/jira/browse/HBASE-20149
> Project: HBase
>  Issue Type: Sub-task
>  Components: build, community, documentation
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-20149.branch-2.0.001.patch, 
> HBASE-20149.branch-2.0.002.patch, HBASE-20149.branch-2.0.003.patch
>
>
> The bin tarball is too fat (Chia-Ping and Josh noticed it on the beta-2 
> vote). A note to the dev list subsequently resulted in suggestion that we 
> just purge dev javadoc (or even all javadoc) from bin tarball (Andrew). Sean 
> was good w/ it and suggested perhaps we could do a javadoc only tgz. Let me 
> look into this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20380) Put up 2.0.0RC0

[stack (JIRA)]

stack created HBASE-20380:
-

 Summary: Put up 2.0.0RC0
 Key: HBASE-20380
 URL: https://issues.apache.org/jira/browse/HBASE-20380
 Project: HBase
  Issue Type: Sub-task
Affects Versions: 2.0.0
Reporter: stack
Assignee: stack
 Fix For: 2.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20379) shadedjars yetus plugin should add a footer link

[Sean Busbey (JIRA)]

Sean Busbey created HBASE-20379:
---

 Summary: shadedjars yetus plugin should add a footer link
 Key: HBASE-20379
 URL: https://issues.apache.org/jira/browse/HBASE-20379
 Project: HBase
  Issue Type: Improvement
  Components: test
Reporter: Sean Busbey
Assignee: Sean Busbey


investigating the failure on HBASE-20219, it would be nice if we posted a 
footer link to what failed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[DISCUSS] RowCounter duplication

[Peter Somogyi]

Hi,

Currently we have 2 RowCounter tools in our
repository: o.a.h.h.mapreduce.RowCounter and o.a.h.h.mapred.RowCounter.
None of them is marked as deprecated but mapred.RowCounter was deprecated
in pre-HBase 1 releases and the annotation was eventually removed
in HBASE-11178.

Do we still want to or need to keep both versions? The mapred tool is not
documented in refguide and the command's usage is minimal. The
mapreduce.RowCounter tool also has more features.

Thanks,
Peter

HBase Developer - Questions

[Stefano Manca]

Dear,

My name is Stefano, I am a young software developer.
In these months I am using HBase as database in a Hadoop cluster, to write
data from Apache Spark with scala language.
May I ask you any question for specific information?

*Q1*: there is a way to insert/update a specific cell as latest field into
the same record?

Example:
ROW COLUMN+CELL
row1  column=CF1:QUAL1, timestamp=1523350296746, value=0.0
row1  column=CF1:QUAL2, timestamp=1523350296746, value=test
row1  column=CF1:QUAL3, timestamp=1523350296746, value=2700
row1  *column=CF2:QUAL4, timestamp=1523350296746, value=01218*
row1  column=CF2:QUAL5, timestamp=1523350296746, value=example

I would like to be sure that the value of the key QUAL4 will be insert as
last field, respect to the other values of the same rowkey (row1).

*Q2*: What is the best way to write in bulk with Spark 2.2? Is the
HBaseContext class available to use the bulkload with Hfiles?


Thank you very much in advance.

Best regards,



*__Stefano Manca*

*Phone: +39 349216059*
*E-mail: ste.manc...@gmail.com *

[jira] [Reopened] (HBASE-20077) add a project health check that ensures the ref guide can be built

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey reopened HBASE-20077:
-

> add a project health check that ensures the ref guide can be built
> --
>
> Key: HBASE-20077
> URL: https://issues.apache.org/jira/browse/HBASE-20077
> Project: HBase
>  Issue Type: New Feature
>  Components: documentation, test
>Reporter: Sean Busbey
>Priority: Minor
>  Labels: beginner
>
> unless someone can think of particulars to check, this command will assemble 
> the book without doing most of the rest of the project:
> {code}
> mvn -pl . clean site --batch-mode -Dmaven.javadoc.skip=true -DskipTests
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Detecting the operating system and CPU architecture
> [INFO] 
> 
> [INFO] os.detected.name: osx
> [INFO] os.detected.arch: x86_64
> [INFO] os.detected.version: 10.11
> [INFO] os.detected.version.major: 10
> [INFO] os.detected.version.minor: 11
> [INFO] os.detected.classifier: osx-x86_64
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache HBase 3.0.0-SNAPSHOT
> [INFO] 
> 
> ...
> [INFO] Executed tasks
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 02:42 min
> [INFO] Finished at: 2018-02-24T14:27:56-06:00
> [INFO] Final Memory: 132M/1015M
> [INFO] 
> 
> {code}
> It's only good for specifically testing the ref guide, since it skips so much 
> (i.e. project compilation and javadocs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-20077) add a project health check that ensures the ref guide can be built

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-20077.
-
Resolution: Duplicate

> add a project health check that ensures the ref guide can be built
> --
>
> Key: HBASE-20077
> URL: https://issues.apache.org/jira/browse/HBASE-20077
> Project: HBase
>  Issue Type: New Feature
>  Components: documentation, test
>Reporter: Sean Busbey
>Priority: Minor
>  Labels: beginner
>
> unless someone can think of particulars to check, this command will assemble 
> the book without doing most of the rest of the project:
> {code}
> mvn -pl . clean site --batch-mode -Dmaven.javadoc.skip=true -DskipTests
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Detecting the operating system and CPU architecture
> [INFO] 
> 
> [INFO] os.detected.name: osx
> [INFO] os.detected.arch: x86_64
> [INFO] os.detected.version: 10.11
> [INFO] os.detected.version.major: 10
> [INFO] os.detected.version.minor: 11
> [INFO] os.detected.classifier: osx-x86_64
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache HBase 3.0.0-SNAPSHOT
> [INFO] 
> 
> ...
> [INFO] Executed tasks
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 02:42 min
> [INFO] Finished at: 2018-02-24T14:27:56-06:00
> [INFO] Final Memory: 132M/1015M
> [INFO] 
> 
> {code}
> It's only good for specifically testing the ref guide, since it skips so much 
> (i.e. project compilation and javadocs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-20077) add a project health check that ensures the ref guide can be built

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-20077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved HBASE-20077.
-
Resolution: Fixed

done by HBASE-15466  you can see the results in current nightly results under 
the "general check" subsection.

> add a project health check that ensures the ref guide can be built
> --
>
> Key: HBASE-20077
> URL: https://issues.apache.org/jira/browse/HBASE-20077
> Project: HBase
>  Issue Type: New Feature
>  Components: documentation, test
>Reporter: Sean Busbey
>Priority: Minor
>  Labels: beginner
>
> unless someone can think of particulars to check, this command will assemble 
> the book without doing most of the rest of the project:
> {code}
> mvn -pl . clean site --batch-mode -Dmaven.javadoc.skip=true -DskipTests
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Detecting the operating system and CPU architecture
> [INFO] 
> 
> [INFO] os.detected.name: osx
> [INFO] os.detected.arch: x86_64
> [INFO] os.detected.version: 10.11
> [INFO] os.detected.version.major: 10
> [INFO] os.detected.version.minor: 11
> [INFO] os.detected.classifier: osx-x86_64
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache HBase 3.0.0-SNAPSHOT
> [INFO] 
> 
> ...
> [INFO] Executed tasks
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 02:42 min
> [INFO] Finished at: 2018-02-24T14:27:56-06:00
> [INFO] Final Memory: 132M/1015M
> [INFO] 
> 
> {code}
> It's only good for specifically testing the ref guide, since it skips so much 
> (i.e. project compilation and javadocs)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20378) Provide a hbck option to cleanup replication barrier for a table

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-20378:
-

 Summary: Provide a hbck option to cleanup replication barrier for 
a table
 Key: HBASE-20378
 URL: https://issues.apache.org/jira/browse/HBASE-20378
 Project: HBase
  Issue Type: Sub-task
Reporter: Duo Zhang


It is not easy to deal with the scenario where a user change the replication 
scope from global to local since it may change the scope back while we are 
cleaning in the background. And I think this a rare operation so just provide 
an hbck option to deal with it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20377) Deal with table in enabling and disabling state when modifying serial replication peer

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-20377:
-

 Summary: Deal with table in enabling and disabling state when 
modifying serial replication peer
 Key: HBASE-20377
 URL: https://issues.apache.org/jira/browse/HBASE-20377
 Project: HBase
  Issue Type: Sub-task
  Components: Replication
Reporter: Duo Zhang


There could be race between reopening regions and enabling table, and also 
between disabling table and write last pushed sequence id for disabled table. 
Maybe we need to wait for the table state to become enabled or disabled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (HBASE-20376) RowCounter and CellCounter documentations are incorrect

[Peter Somogyi (JIRA)]

Peter Somogyi created HBASE-20376:
-

 Summary: RowCounter and CellCounter documentations are incorrect
 Key: HBASE-20376
 URL: https://issues.apache.org/jira/browse/HBASE-20376
 Project: HBase
  Issue Type: Bug
  Components: documentation, mapreduce
Affects Versions: 2.0.0
Reporter: Peter Somogyi
Assignee: Peter Somogyi
 Fix For: 2.0.0


The documentation of RowCounter and CellCounter in refguide needs some 
improvement. Help messages also need some tuning.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-19843) Allow temporarily skipping the creation of remote writer for SynchronousReplicationWALProvider

[Duo Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-19843.
---
Resolution: Duplicate

> Allow temporarily skipping the creation of remote writer for 
> SynchronousReplicationWALProvider
> --
>
> Key: HBASE-19843
> URL: https://issues.apache.org/jira/browse/HBASE-19843
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Duo Zhang
>Priority: Major
>
> If the remote cluster is broken and we want to downgrade the local cluster to 
> not write WAL to remote cluster, we need to reopen the region to switch back 
> to use the normal WAL.
> But we need to flush before reopening a region, and the flush need to write a 
> flush marker to WAL. Since the WAL has already been broken, this can not be 
> done...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-19080) Implement a procedure to convert RS from A to DA

[Duo Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-19080.
---
   Resolution: Duplicate
Fix Version/s: (was: 3.0.0)

> Implement a procedure to convert RS from A to DA
> 
>
> Key: HBASE-19080
> URL: https://issues.apache.org/jira/browse/HBASE-19080
> Project: HBase
>  Issue Type: Sub-task
>  Components: Replication
>Reporter: Duo Zhang
>Priority: Major
>  Labels: HBASE-19064
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (HBASE-19081) Implement a procedure to convert RS from S to DA

[Duo Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HBASE-19081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-19081.
---
   Resolution: Duplicate
Fix Version/s: (was: 3.0.0)

> Implement a procedure to convert RS from S to DA
> 
>
> Key: HBASE-19081
> URL: https://issues.apache.org/jira/browse/HBASE-19081
> Project: HBase
>  Issue Type: Sub-task
>  Components: Replication
>Reporter: Duo Zhang
>Assignee: Guanghao Zhang
>Priority: Major
>  Labels: HBASE-19064
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)