[jira] [Resolved] (HBASE-16718) TestMobFlushSnapshotFromClient,TestFlushSnapshotFromClient, TestRestoreFlushSnapshotFromClient are failing in QA builds

[Jingcheng Du (JIRA)]

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

Jingcheng Du resolved HBASE-16718.
--
Resolution: Duplicate

> TestMobFlushSnapshotFromClient,TestFlushSnapshotFromClient, 
> TestRestoreFlushSnapshotFromClient are failing in QA builds
> ---
>
> Key: HBASE-16718
> URL: https://issues.apache.org/jira/browse/HBASE-16718
> Project: HBase
>  Issue Type: Bug
>Reporter: ramkrishna.s.vasudevan
> Fix For: 2.0.0
>
>
> We could see failures in QA builds frequently with the test cases mentioned 
> in the title of the JIRA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-16798) Integrate MultiRowMutation CPEP into HBase core

[Jerry He (JIRA)]

Jerry He created HBASE-16798:


 Summary: Integrate MultiRowMutation CPEP into HBase core
 Key: HBASE-16798
 URL: https://issues.apache.org/jira/browse/HBASE-16798
 Project: HBase
  Issue Type: Sub-task
Reporter: Jerry He


Integrate MultiRowMutation CPEP into HBase core as discussed in the parent task.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-16797) Integrate TokenProvider to HBase core

[Jerry He (JIRA)]

Jerry He created HBASE-16797:


 Summary: Integrate TokenProvider to HBase core
 Key: HBASE-16797
 URL: https://issues.apache.org/jira/browse/HBASE-16797
 Project: HBase
  Issue Type: Sub-task
Reporter: Jerry He


Integrate TokenProvider to HBase core as discussed in the parent task.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-16796) Correct RpcServer responseSize and requestSize to account for cellScanner payload

[Jerry He (JIRA)]

Jerry He created HBASE-16796:


 Summary: Correct RpcServer responseSize and requestSize to account 
for cellScanner payload
 Key: HBASE-16796
 URL: https://issues.apache.org/jira/browse/HBASE-16796
 Project: HBase
  Issue Type: Bug
Reporter: Jerry He
Assignee: Jerry He


The reponseSize and requestSize on the RpcServer don't seem to account for the 
cellScanner payload.  We should correct them.
The metrics numbers and the logging for reponseTooLarge  and TooSlow won't  
show up correctly otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Need hand-holding for 1.1.7 release management

[Ted Yu]

Was there any action which was required for the release but is not
documented already ?

Thanks

On Mon, Sep 26, 2016 at 1:33 PM, Misty Stanley-Jones 
wrote:

> Thanks, I have followed those steps and now I am attempting to build the
> RC. Let's see how it goes.
>
> On Tue, Sep 27, 2016, at 05:20 AM, Sean Busbey wrote:
> > My ~/.m2/settings.xml file looks like the example from the "pushing
> > stuff to maven" guide[1]:
> >
> > http://maven.apache.org/SETTINGS/1.0.0;
> >   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> >   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
> >   http://maven.apache.org/xsd/settings-1.0.0.xsd;>
> >   
> > 
> > 
> > 
> >   apache.releases.https
> >   busbey
> >   
> >   
> >   
> > 
> >   
> > 
> >
> > I don't bother including a section for publishing SNAPSHOTs because I
> > don't publish SNAPSHOTs.
> >
> > Note that you'll need to follow the maven password encryption guide to
> > avoid storing your plaintext ASF creds[2] and you should use Maven
> > 3.2.1+ so that you don't need to put the password(s) on the command
> > invocation.
> >
> >
> > [1]: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
> > [2]: http://maven.apache.org/guides/mini/guide-encryption.html
> >
> > On Mon, Sep 26, 2016 at 11:33 AM, Misty Stanley-Jones 
> > wrote:
> > > Is anyone around who can help me with some of the release management
> > > steps? I think I have updated the KEYS file correctly, but now I am
> > > stuck on what my ~/.m2/settings.xml should look like. I think I'm most
> > > of the way there...
> >
> >
> >
> > --
> > busbey
>

[jira] [Created] (HBASE-16795) Revisit 'in project Maven repo' checked in as part of HBASE-14785

[Andrew Purtell (JIRA)]

Andrew Purtell created HBASE-16795:
--

 Summary: Revisit 'in project Maven repo' checked in as part of 
HBASE-14785
 Key: HBASE-16795
 URL: https://issues.apache.org/jira/browse/HBASE-16795
 Project: HBase
  Issue Type: Bug
Reporter: Andrew Purtell


I did a naive update of docs on branch-1.1 from master like so:
{noformat}
$ git co master src
...
{noformat}
and the result failed a RAT check. Looking at rat.txt I noticed we are 
including binaries in our source tarball, checked in as part of HBASE-14785. 
{noformat}
HBASE-14785 Addendum: Add an in-project Maven repo

 src/main/site/resources/css/site.css |   1 -
 .../maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.jar  | Bin 0 -> 
344936 bytes
 .../maven-fluido-skin/1.5-HBASE/maven-fluido-skin-1.5-HBASE.pom  | 718 

 .../maven/skins/maven-fluido-skin/maven-metadata-local.xml   |  12 +
 4 files changed, 730 insertions(+), 1 deletion(-)
{noformat}
This was not the cause of the audit check failure. This change has been 
committed for over a year. Let's make sure we have discussed this and 
determined it is appropriate. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Fixed: HBase Generate Website

[Ted Yu]

I asked the question because from your original email, it seemed that the
xml files were newly added.

As you just said, this is another issue (than the one you first mentioned).
So I still wonder what regression you discovered.

Cheers

On Sun, Oct 9, 2016 at 9:37 AM, Andrew Purtell  wrote:

> Great, this is another issue. I will file a JIRA for that. Why did you ask
> me to find this out when it took you barely a few minutes? That is a
> rhetorical question, no need to actually answer.
>
>
> On Sun, Oct 9, 2016 at 9:27 AM, Ted Yu  wrote:
>
> > Under hbase-site, I found two xml files:
> >
> > ./0.94/hbase-default.xml
> > ./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
> >
> > For the second one:
> >
> > git log
> > ./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
> > commit 80bb21927918b30e88602571b9ba766edd3484ed
> > Author: Misty Stanley-Jones 
> > Date:   Mon Dec 7 13:27:40 2015 -0800
> >
> > Initial import from hbase repo 2dc53cb992915ff7c0402290eb723d
> > 9422877985
> >
> > Was this the file you were talking about ?
> >
> > If not, which one(s) should be looked at ?
> >
> > If you're talking about reverting the site push, go ahead do that while
> the
> > discussion proceeds.
> >
> > Cheers
> >
> > On Sun, Oct 9, 2016 at 9:21 AM, Andrew Purtell  >
> > wrote:
> >
> > > This is your problem. Take ownership. Fix it or I'll revert it.
> > >
> > > > On Oct 9, 2016, at 9:05 AM, Ted Yu  wrote:
> > > >
> > > > Isn't the RAT check part of the build which generated the 256K patch
> ?
> > > > If not, we should add it.
> > > >
> > > > Which XML file misses the license header ?
> > > >
> > > > Is this related to HBASE-16793 ?
> > > >
> > > > On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell <
> > andrew.purt...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> I tried to copy latest docs from master into the 1.1.7 RC yesterday
> > but
> > > >> the result then failed a RAT check on an XML file missing a header
> and
> > > some
> > > >> jars in src/main/resources . I have not checked today if the
> situation
> > > is
> > > >> better. Those jars will be binaries appearing in our source
> tarballs.
> > > We ok
> > > >> with that?
> > > >>
> > > >>> On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> > > >>>
> > > >>> I pushed the artifacts.
> > > >>>
> > > >>> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> > > >>> jenk...@builds.apache.org> wrote:
> > > >>>
> > >  Build status: Fixed
> > > 
> > >  If successful, the website and docs have been generated. To update
> > the
> > >  live site, follow the instructions below. If failed, skip to the
> > > bottom
> > > >> of
> > >  this email.
> > > 
> > >  Use the following commands to download the patch and apply it to a
> > > clean
> > >  branch based on origin/asf-site. If you prefer to keep the
> > hbase-site
> > > >> repo
> > >  around permanently, you can skip the clone step.
> > > 
> > >  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> > > 
> > >  cd hbase-site
> > >  wget -O- https://builds.apache.org/job/
> hbase_generate_website/371/
> > >  artifact/website.patch.zip | funzip >
> e06c3676f1273f033e3e185ee9c1ec
> > >  52c1c7cb31.patch
> > >  git fetch
> > >  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> > >  origin/asf-site
> > >  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec
> > > 52c1c7cb31.patch
> > > 
> > >  At this point, you can preview the changes by opening index.html
> or
> > > any
> > > >> of
> > >  the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
> > > >> 85ee9c1ec52c1c7cb31
> > >  branch.
> > > 
> > >  There are lots of spurious changes, such as timestamps and CSS
> > styles
> > > in
> > >  tables, so a generic git diff is not very useful. To see a list of
> > > files
> > >  that have been added, deleted, renamed, changed type, or are
> > otherwise
> > >  interesting, use the following command:
> > > 
> > >  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> > > 
> > >  To see only files that had 100 or more lines changed:
> > > 
> > >  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> > > 
> > >  When you are satisfied, publish your changes to origin/asf-site
> > using
> > >  these commands:
> > > 
> > >  git commit --allow-empty -m "Empty commit" # to work around a
> > current
> > >  ASF INFRA bug
> > >  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
> > >  52c1c7cb31:asf-site
> > >  git checkout asf-site
> > >  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> > > 
> > >  Changes take a couple of minutes to be propagated. You can verify
> > > >> whether
> > > 

Re: Fixed: HBase Generate Website

[Andrew Purtell]

Great, this is another issue. I will file a JIRA for that. Why did you ask
me to find this out when it took you barely a few minutes? That is a
rhetorical question, no need to actually answer.


On Sun, Oct 9, 2016 at 9:27 AM, Ted Yu  wrote:

> Under hbase-site, I found two xml files:
>
> ./0.94/hbase-default.xml
> ./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
>
> For the second one:
>
> git log
> ./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
> commit 80bb21927918b30e88602571b9ba766edd3484ed
> Author: Misty Stanley-Jones 
> Date:   Mon Dec 7 13:27:40 2015 -0800
>
> Initial import from hbase repo 2dc53cb992915ff7c0402290eb723d
> 9422877985
>
> Was this the file you were talking about ?
>
> If not, which one(s) should be looked at ?
>
> If you're talking about reverting the site push, go ahead do that while the
> discussion proceeds.
>
> Cheers
>
> On Sun, Oct 9, 2016 at 9:21 AM, Andrew Purtell 
> wrote:
>
> > This is your problem. Take ownership. Fix it or I'll revert it.
> >
> > > On Oct 9, 2016, at 9:05 AM, Ted Yu  wrote:
> > >
> > > Isn't the RAT check part of the build which generated the 256K patch ?
> > > If not, we should add it.
> > >
> > > Which XML file misses the license header ?
> > >
> > > Is this related to HBASE-16793 ?
> > >
> > > On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell <
> andrew.purt...@gmail.com
> > >
> > > wrote:
> > >
> > >> I tried to copy latest docs from master into the 1.1.7 RC yesterday
> but
> > >> the result then failed a RAT check on an XML file missing a header and
> > some
> > >> jars in src/main/resources . I have not checked today if the situation
> > is
> > >> better. Those jars will be binaries appearing in our source tarballs.
> > We ok
> > >> with that?
> > >>
> > >>> On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> > >>>
> > >>> I pushed the artifacts.
> > >>>
> > >>> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> > >>> jenk...@builds.apache.org> wrote:
> > >>>
> >  Build status: Fixed
> > 
> >  If successful, the website and docs have been generated. To update
> the
> >  live site, follow the instructions below. If failed, skip to the
> > bottom
> > >> of
> >  this email.
> > 
> >  Use the following commands to download the patch and apply it to a
> > clean
> >  branch based on origin/asf-site. If you prefer to keep the
> hbase-site
> > >> repo
> >  around permanently, you can skip the clone step.
> > 
> >  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> > 
> >  cd hbase-site
> >  wget -O- https://builds.apache.org/job/hbase_generate_website/371/
> >  artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
> >  52c1c7cb31.patch
> >  git fetch
> >  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >  origin/asf-site
> >  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec
> > 52c1c7cb31.patch
> > 
> >  At this point, you can preview the changes by opening index.html or
> > any
> > >> of
> >  the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
> > >> 85ee9c1ec52c1c7cb31
> >  branch.
> > 
> >  There are lots of spurious changes, such as timestamps and CSS
> styles
> > in
> >  tables, so a generic git diff is not very useful. To see a list of
> > files
> >  that have been added, deleted, renamed, changed type, or are
> otherwise
> >  interesting, use the following command:
> > 
> >  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> > 
> >  To see only files that had 100 or more lines changed:
> > 
> >  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> > 
> >  When you are satisfied, publish your changes to origin/asf-site
> using
> >  these commands:
> > 
> >  git commit --allow-empty -m "Empty commit" # to work around a
> current
> >  ASF INFRA bug
> >  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
> >  52c1c7cb31:asf-site
> >  git checkout asf-site
> >  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> > 
> >  Changes take a couple of minutes to be propagated. You can verify
> > >> whether
> >  they have been propagated by looking at the Last Published date at
> the
> >  bottom of http://hbase.apache.org/. It should match the date in the
> >  index.html on the asf-site branch in Git.
> > 
> >  As a courtesy- reply-all to this email to let other committers know
> > you
> >  pushed the site.
> > 
> > 
> > 
> >  If failed, see https://builds.apache.org/job/
> > >> hbase_generate_website/371/
> >  console
> > >>
> >
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: Fixed: HBase Generate Website

[Ted Yu]

Under hbase-site, I found two xml files:

./0.94/hbase-default.xml
./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml

For the second one:

git log
./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
commit 80bb21927918b30e88602571b9ba766edd3484ed
Author: Misty Stanley-Jones 
Date:   Mon Dec 7 13:27:40 2015 -0800

Initial import from hbase repo 2dc53cb992915ff7c0402290eb723d9422877985

Was this the file you were talking about ?

If not, which one(s) should be looked at ?

If you're talking about reverting the site push, go ahead do that while the
discussion proceeds.

Cheers

On Sun, Oct 9, 2016 at 9:21 AM, Andrew Purtell 
wrote:

> This is your problem. Take ownership. Fix it or I'll revert it.
>
> > On Oct 9, 2016, at 9:05 AM, Ted Yu  wrote:
> >
> > Isn't the RAT check part of the build which generated the 256K patch ?
> > If not, we should add it.
> >
> > Which XML file misses the license header ?
> >
> > Is this related to HBASE-16793 ?
> >
> > On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell  >
> > wrote:
> >
> >> I tried to copy latest docs from master into the 1.1.7 RC yesterday but
> >> the result then failed a RAT check on an XML file missing a header and
> some
> >> jars in src/main/resources . I have not checked today if the situation
> is
> >> better. Those jars will be binaries appearing in our source tarballs.
> We ok
> >> with that?
> >>
> >>> On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> >>>
> >>> I pushed the artifacts.
> >>>
> >>> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> >>> jenk...@builds.apache.org> wrote:
> >>>
>  Build status: Fixed
> 
>  If successful, the website and docs have been generated. To update the
>  live site, follow the instructions below. If failed, skip to the
> bottom
> >> of
>  this email.
> 
>  Use the following commands to download the patch and apply it to a
> clean
>  branch based on origin/asf-site. If you prefer to keep the hbase-site
> >> repo
>  around permanently, you can skip the clone step.
> 
>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> 
>  cd hbase-site
>  wget -O- https://builds.apache.org/job/hbase_generate_website/371/
>  artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
>  52c1c7cb31.patch
>  git fetch
>  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>  origin/asf-site
>  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec
> 52c1c7cb31.patch
> 
>  At this point, you can preview the changes by opening index.html or
> any
> >> of
>  the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
> >> 85ee9c1ec52c1c7cb31
>  branch.
> 
>  There are lots of spurious changes, such as timestamps and CSS styles
> in
>  tables, so a generic git diff is not very useful. To see a list of
> files
>  that have been added, deleted, renamed, changed type, or are otherwise
>  interesting, use the following command:
> 
>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> 
>  To see only files that had 100 or more lines changed:
> 
>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> 
>  When you are satisfied, publish your changes to origin/asf-site using
>  these commands:
> 
>  git commit --allow-empty -m "Empty commit" # to work around a current
>  ASF INFRA bug
>  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
>  52c1c7cb31:asf-site
>  git checkout asf-site
>  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> 
>  Changes take a couple of minutes to be propagated. You can verify
> >> whether
>  they have been propagated by looking at the Last Published date at the
>  bottom of http://hbase.apache.org/. It should match the date in the
>  index.html on the asf-site branch in Git.
> 
>  As a courtesy- reply-all to this email to let other committers know
> you
>  pushed the site.
> 
> 
> 
>  If failed, see https://builds.apache.org/job/
> >> hbase_generate_website/371/
>  console
> >>
>

Re: [DISCUSS] Add CoC guideline about private emails

[Andrew Purtell]

Obviously those of us not on these private threads have no idea this is going 
on. (Smile) Agreed it's a problem, and it would be good to clarify this 
somewhere. CoC seems reasonable. 

> On Oct 9, 2016, at 9:00 AM, Misty Stanley-Jones  wrote:
> 
> There are a few people who routinely email me privately about non-personal 
> matters where I'm not the only one with the answer. In many cases I reply, 
> adding dev@ to the CC, and I've also asked the people to use the mailing 
> lists instead of emailing me privately, but the message has obviously not 
> gotten through. I'm not just being fussy and I know I'm not the only one. 
> Taking it off-list has consequences:
> 
> - information is siloed / single points of failure
> - if I'm on vacation or otherwise not immediately available, you're blocked 
> from getting the thing done 
> - others lose out on the chance to contribute to the community
> - decisions made via private email actually violate our community standards, 
> except in some very specific instances such as software security bugs
> - it's annoying and exclusionary 
> - it can be intimidating
> - it can lead to inadvertently or unintentionally taking credit for someone 
> else's work
> 
> I'd like to propose that we add something to the code of conduct to 
> discourage using private email threads in the hbase community except for 
> social or personal conversations. Thoughts?
> 
> 

Re: Fixed: HBase Generate Website

[Andrew Purtell]

This is your problem. Take ownership. Fix it or I'll revert it. 

> On Oct 9, 2016, at 9:05 AM, Ted Yu  wrote:
> 
> Isn't the RAT check part of the build which generated the 256K patch ?
> If not, we should add it.
> 
> Which XML file misses the license header ?
> 
> Is this related to HBASE-16793 ?
> 
> On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell 
> wrote:
> 
>> I tried to copy latest docs from master into the 1.1.7 RC yesterday but
>> the result then failed a RAT check on an XML file missing a header and some
>> jars in src/main/resources . I have not checked today if the situation is
>> better. Those jars will be binaries appearing in our source tarballs. We ok
>> with that?
>> 
>>> On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
>>> 
>>> I pushed the artifacts.
>>> 
>>> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
>>> jenk...@builds.apache.org> wrote:
>>> 
 Build status: Fixed
 
 If successful, the website and docs have been generated. To update the
 live site, follow the instructions below. If failed, skip to the bottom
>> of
 this email.
 
 Use the following commands to download the patch and apply it to a clean
 branch based on origin/asf-site. If you prefer to keep the hbase-site
>> repo
 around permanently, you can skip the clone step.
 
 git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
 
 cd hbase-site
 wget -O- https://builds.apache.org/job/hbase_generate_website/371/
 artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
 52c1c7cb31.patch
 git fetch
 git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
 origin/asf-site
 git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
 
 At this point, you can preview the changes by opening index.html or any
>> of
 the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
>> 85ee9c1ec52c1c7cb31
 branch.
 
 There are lots of spurious changes, such as timestamps and CSS styles in
 tables, so a generic git diff is not very useful. To see a list of files
 that have been added, deleted, renamed, changed type, or are otherwise
 interesting, use the following command:
 
 git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
 
 To see only files that had 100 or more lines changed:
 
 git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
 
 When you are satisfied, publish your changes to origin/asf-site using
 these commands:
 
 git commit --allow-empty -m "Empty commit" # to work around a current
 ASF INFRA bug
 git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
 52c1c7cb31:asf-site
 git checkout asf-site
 git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
 
 Changes take a couple of minutes to be propagated. You can verify
>> whether
 they have been propagated by looking at the Last Published date at the
 bottom of http://hbase.apache.org/. It should match the date in the
 index.html on the asf-site branch in Git.
 
 As a courtesy- reply-all to this email to let other committers know you
 pushed the site.
 
 
 
 If failed, see https://builds.apache.org/job/
>> hbase_generate_website/371/
 console
>> 

Re: Fixed: HBase Generate Website

[Sean Busbey]

ASF policy prohibits binaries in official release artifacts.

On Oct 9, 2016 10:43, "Andrew Purtell"  wrote:

> I tried to copy latest docs from master into the 1.1.7 RC yesterday but
> the result then failed a RAT check on an XML file missing a header and some
> jars in src/main/resources . I have not checked today if the situation is
> better. Those jars will be binaries appearing in our source tarballs. We ok
> with that?
>
> > On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> >
> > I pushed the artifacts.
> >
> > On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> >> Build status: Fixed
> >>
> >> If successful, the website and docs have been generated. To update the
> >> live site, follow the instructions below. If failed, skip to the bottom
> of
> >> this email.
> >>
> >> Use the following commands to download the patch and apply it to a clean
> >> branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> >> around permanently, you can skip the clone step.
> >>
> >>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >>
> >>  cd hbase-site
> >>  wget -O- https://builds.apache.org/job/hbase_generate_website/371/
> >> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
> >> 52c1c7cb31.patch
> >>  git fetch
> >>  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >> origin/asf-site
> >>  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
> >>
> >> At this point, you can preview the changes by opening index.html or any
> of
> >> the other HTML pages in your local asf-site-
> e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >> branch.
> >>
> >> There are lots of spurious changes, such as timestamps and CSS styles in
> >> tables, so a generic git diff is not very useful. To see a list of files
> >> that have been added, deleted, renamed, changed type, or are otherwise
> >> interesting, use the following command:
> >>
> >>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >>
> >> To see only files that had 100 or more lines changed:
> >>
> >>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >>
> >> When you are satisfied, publish your changes to origin/asf-site using
> >> these commands:
> >>
> >>  git commit --allow-empty -m "Empty commit" # to work around a current
> >> ASF INFRA bug
> >>  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
> >> 52c1c7cb31:asf-site
> >>  git checkout asf-site
> >>  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >>
> >> Changes take a couple of minutes to be propagated. You can verify
> whether
> >> they have been propagated by looking at the Last Published date at the
> >> bottom of http://hbase.apache.org/. It should match the date in the
> >> index.html on the asf-site branch in Git.
> >>
> >> As a courtesy- reply-all to this email to let other committers know you
> >> pushed the site.
> >>
> >>
> >>
> >> If failed, see https://builds.apache.org/job/
> hbase_generate_website/371/
> >> console
>

Re: Fixed: HBase Generate Website

[Ted Yu]

Isn't the RAT check part of the build which generated the 256K patch ?
If not, we should add it.

Which XML file misses the license header ?

Is this related to HBASE-16793 ?

On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell 
wrote:

> I tried to copy latest docs from master into the 1.1.7 RC yesterday but
> the result then failed a RAT check on an XML file missing a header and some
> jars in src/main/resources . I have not checked today if the situation is
> better. Those jars will be binaries appearing in our source tarballs. We ok
> with that?
>
> > On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> >
> > I pushed the artifacts.
> >
> > On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> > jenk...@builds.apache.org> wrote:
> >
> >> Build status: Fixed
> >>
> >> If successful, the website and docs have been generated. To update the
> >> live site, follow the instructions below. If failed, skip to the bottom
> of
> >> this email.
> >>
> >> Use the following commands to download the patch and apply it to a clean
> >> branch based on origin/asf-site. If you prefer to keep the hbase-site
> repo
> >> around permanently, you can skip the clone step.
> >>
> >>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
> >>
> >>  cd hbase-site
> >>  wget -O- https://builds.apache.org/job/hbase_generate_website/371/
> >> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
> >> 52c1c7cb31.patch
> >>  git fetch
> >>  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >> origin/asf-site
> >>  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
> >>
> >> At this point, you can preview the changes by opening index.html or any
> of
> >> the other HTML pages in your local asf-site-e06c3676f1273f033e3e1
> 85ee9c1ec52c1c7cb31
> >> branch.
> >>
> >> There are lots of spurious changes, such as timestamps and CSS styles in
> >> tables, so a generic git diff is not very useful. To see a list of files
> >> that have been added, deleted, renamed, changed type, or are otherwise
> >> interesting, use the following command:
> >>
> >>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> >>
> >> To see only files that had 100 or more lines changed:
> >>
> >>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> >>
> >> When you are satisfied, publish your changes to origin/asf-site using
> >> these commands:
> >>
> >>  git commit --allow-empty -m "Empty commit" # to work around a current
> >> ASF INFRA bug
> >>  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
> >> 52c1c7cb31:asf-site
> >>  git checkout asf-site
> >>  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> >>
> >> Changes take a couple of minutes to be propagated. You can verify
> whether
> >> they have been propagated by looking at the Last Published date at the
> >> bottom of http://hbase.apache.org/. It should match the date in the
> >> index.html on the asf-site branch in Git.
> >>
> >> As a courtesy- reply-all to this email to let other committers know you
> >> pushed the site.
> >>
> >>
> >>
> >> If failed, see https://builds.apache.org/job/
> hbase_generate_website/371/
> >> console
>

Re: [DISCUSS] Add CoC guideline about private emails

[Dima Spivak]

+1. It's always a good idea to codify community best practices, whether
technical or social.

On Sunday, October 9, 2016, Misty Stanley-Jones  wrote:

> There are a few people who routinely email me privately about non-personal
> matters where I'm not the only one with the answer. In many cases I reply,
> adding dev@ to the CC, and I've also asked the people to use the mailing
> lists instead of emailing me privately, but the message has obviously not
> gotten through. I'm not just being fussy and I know I'm not the only one.
> Taking it off-list has consequences:
>
> - information is siloed / single points of failure
> - if I'm on vacation or otherwise not immediately available, you're
> blocked from getting the thing done
> - others lose out on the chance to contribute to the community
> - decisions made via private email actually violate our community
> standards, except in some very specific instances such as software security
> bugs
> - it's annoying and exclusionary
> - it can be intimidating
> - it can lead to inadvertently or unintentionally taking credit for
> someone else's work
>
> I'd like to propose that we add something to the code of conduct to
> discourage using private email threads in the hbase community except for
> social or personal conversations. Thoughts?
>
>
>

-- 
-Dima

[DISCUSS] Add CoC guideline about private emails

[Misty Stanley-Jones]

There are a few people who routinely email me privately about non-personal 
matters where I'm not the only one with the answer. In many cases I reply, 
adding dev@ to the CC, and I've also asked the people to use the mailing lists 
instead of emailing me privately, but the message has obviously not gotten 
through. I'm not just being fussy and I know I'm not the only one. Taking it 
off-list has consequences:

- information is siloed / single points of failure
- if I'm on vacation or otherwise not immediately available, you're blocked 
from getting the thing done 
- others lose out on the chance to contribute to the community
- decisions made via private email actually violate our community standards, 
except in some very specific instances such as software security bugs
- it's annoying and exclusionary 
- it can be intimidating
- it can lead to inadvertently or unintentionally taking credit for someone 
else's work

I'd like to propose that we add something to the code of conduct to discourage 
using private email threads in the hbase community except for social or 
personal conversations. Thoughts?

Re: Fixed: HBase Generate Website

[Andrew Purtell]

I tried to copy latest docs from master into the 1.1.7 RC yesterday but the 
result then failed a RAT check on an XML file missing a header and some jars in 
src/main/resources . I have not checked today if the situation is better. Those 
jars will be binaries appearing in our source tarballs. We ok with that? 

> On Oct 9, 2016, at 8:14 AM, Ted Yu  wrote:
> 
> I pushed the artifacts.
> 
> On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
> 
>> Build status: Fixed
>> 
>> If successful, the website and docs have been generated. To update the
>> live site, follow the instructions below. If failed, skip to the bottom of
>> this email.
>> 
>> Use the following commands to download the patch and apply it to a clean
>> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
>> around permanently, you can skip the clone step.
>> 
>>  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>> 
>>  cd hbase-site
>>  wget -O- https://builds.apache.org/job/hbase_generate_website/371/
>> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
>> 52c1c7cb31.patch
>>  git fetch
>>  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>> origin/asf-site
>>  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
>> 
>> At this point, you can preview the changes by opening index.html or any of
>> the other HTML pages in your local 
>> asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>> branch.
>> 
>> There are lots of spurious changes, such as timestamps and CSS styles in
>> tables, so a generic git diff is not very useful. To see a list of files
>> that have been added, deleted, renamed, changed type, or are otherwise
>> interesting, use the following command:
>> 
>>  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>> 
>> To see only files that had 100 or more lines changed:
>> 
>>  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>> 
>> When you are satisfied, publish your changes to origin/asf-site using
>> these commands:
>> 
>>  git commit --allow-empty -m "Empty commit" # to work around a current
>> ASF INFRA bug
>>  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
>> 52c1c7cb31:asf-site
>>  git checkout asf-site
>>  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>> 
>> Changes take a couple of minutes to be propagated. You can verify whether
>> they have been propagated by looking at the Last Published date at the
>> bottom of http://hbase.apache.org/. It should match the date in the
>> index.html on the asf-site branch in Git.
>> 
>> As a courtesy- reply-all to this email to let other committers know you
>> pushed the site.
>> 
>> 
>> 
>> If failed, see https://builds.apache.org/job/hbase_generate_website/371/
>> console

[jira] [Created] (HBASE-16794) TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky

[ChiaPing Tsai (JIRA)]

ChiaPing Tsai created HBASE-16794:
-

 Summary: 
TestDispatchMergingRegionsProcedure#testMergeRegionsConcurrently is flaky
 Key: HBASE-16794
 URL: https://issues.apache.org/jira/browse/HBASE-16794
 Project: HBase
  Issue Type: Test
Reporter: ChiaPing Tsai
Priority: Minor


The default count of merge thread is 1, so the merge requests submitted by 
TDMRP#testMergeRegionsConcurrently will be processed sequentially. If we are 
too early to check the region states, it will introduce the error.
This patch checks the number of running merge task instead of the regions 
states.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Fixed: HBase Generate Website

[Ted Yu]

I pushed the artifacts.

On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> Build status: Fixed
>
> If successful, the website and docs have been generated. To update the
> live site, follow the instructions below. If failed, skip to the bottom of
> this email.
>
> Use the following commands to download the patch and apply it to a clean
> branch based on origin/asf-site. If you prefer to keep the hbase-site repo
> around permanently, you can skip the clone step.
>
>   git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
>
>   cd hbase-site
>   wget -O- https://builds.apache.org/job/hbase_generate_website/371/
> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec
> 52c1c7cb31.patch
>   git fetch
>   git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> origin/asf-site
>   git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
>
> At this point, you can preview the changes by opening index.html or any of
> the other HTML pages in your local 
> asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
> branch.
>
> There are lots of spurious changes, such as timestamps and CSS styles in
> tables, so a generic git diff is not very useful. To see a list of files
> that have been added, deleted, renamed, changed type, or are otherwise
> interesting, use the following command:
>
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
>
> To see only files that had 100 or more lines changed:
>
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
>
> When you are satisfied, publish your changes to origin/asf-site using
> these commands:
>
>   git commit --allow-empty -m "Empty commit" # to work around a current
> ASF INFRA bug
>   git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec
> 52c1c7cb31:asf-site
>   git checkout asf-site
>   git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31
>
> Changes take a couple of minutes to be propagated. You can verify whether
> they have been propagated by looking at the Last Published date at the
> bottom of http://hbase.apache.org/. It should match the date in the
> index.html on the asf-site branch in Git.
>
> As a courtesy- reply-all to this email to let other committers know you
> pushed the site.
>
>
>
> If failed, see https://builds.apache.org/job/hbase_generate_website/371/
> console

Re: Pushing website

[Misty Stanley-Jones]

In the daily email that goes to dev@

> On Oct 9, 2016, at 12:38 AM, Ted Yu  wrote:
> 
> Misty:
> Where can I find instructions for pushing latest green website build ?
> 
> Cheers

[jira] [Resolved] (HBASE-16683) Address review comments for mega patch of backup / restore feature

[Ted Yu (JIRA)]

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

Ted Yu resolved HBASE-16683.

  Resolution: Fixed
Hadoop Flags: Reviewed

> Address review comments for mega patch of backup / restore feature
> --
>
> Key: HBASE-16683
> URL: https://issues.apache.org/jira/browse/HBASE-16683
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>  Labels: backup
> Attachments: 16683.v1.txt
>
>
> There're review comments for the mega patch posted over HBASE-14123.
> See https://reviews.apache.org/r/51823/
> This issue is for addressing review comments in HBASE-7912 branch.
> Mega patch for master branch would be posted / tested on HBASE-14123.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (HBASE-16685) Revisit execution of SnapshotCopy in MapReduceBackupCopyService

[Ted Yu (JIRA)]

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

Ted Yu resolved HBASE-16685.

Resolution: Not A Problem

After code refactoring, this is no longer applicable.

> Revisit execution of SnapshotCopy in MapReduceBackupCopyService
> ---
>
> Key: HBASE-16685
> URL: https://issues.apache.org/jira/browse/HBASE-16685
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>  Labels: backup
>
> During code review of backup / restore, Matteo raised comment on the 
> following code:
> {code}
> res = snapshotCp.run(options);
> {code}
> I think this will be a first time where HBase server has a direct dependency 
> on a MR job.
> also we need to revisit this code to avoid having one handler blocked for N 
> hours while we are doing a copy.
> This issue is to address the above comment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-16793) Exclude shaded protobuf files from rat check

[Duo Zhang (JIRA)]

Duo Zhang created HBASE-16793:
-

 Summary: Exclude shaded protobuf files from rat check
 Key: HBASE-16793
 URL: https://issues.apache.org/jira/browse/HBASE-16793
 Project: HBase
  Issue Type: Bug
  Components: build
Affects Versions: 2.0.0
Reporter: Duo Zhang
Assignee: Duo Zhang
 Fix For: 2.0.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (HBASE-16792) Reuse KeyValue.KeyOnlyKeyValue in BufferedDataBlockEncoder.SeekerState

[binlijin (JIRA)]

binlijin created HBASE-16792:


 Summary: Reuse KeyValue.KeyOnlyKeyValue in 
BufferedDataBlockEncoder.SeekerState
 Key: HBASE-16792
 URL: https://issues.apache.org/jira/browse/HBASE-16792
 Project: HBase
  Issue Type: Improvement
Reporter: binlijin
 Attachments: HBASE-16792_master.patch

When every SeekerState#invalidate will new a fresh KeyValue.KeyOnlyKeyValue, we 
should reuse it.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Fixed: HBase Generate Website

[Apache Jenkins Server]

Build status: Fixed

If successful, the website and docs have been generated. To update the live 
site, follow the instructions below. If failed, skip to the bottom of this 
email.

Use the following commands to download the patch and apply it to a clean branch 
based on origin/asf-site. If you prefer to keep the hbase-site repo around 
permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- 
https://builds.apache.org/job/hbase_generate_website/371/artifact/website.patch.zip
 | funzip > e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch
  git fetch
  git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31 
origin/asf-site
  git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.patch

At this point, you can preview the changes by opening index.html or any of the 
other HTML pages in your local 
asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31 branch.

There are lots of spurious changes, such as timestamps and CSS styles in 
tables, so a generic git diff is not very useful. To see a list of files that 
have been added, deleted, renamed, changed type, or are otherwise interesting, 
use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

When you are satisfied, publish your changes to origin/asf-site using these 
commands:

  git commit --allow-empty -m "Empty commit" # to work around a current ASF 
INFRA bug
  git push origin asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31:asf-site
  git checkout asf-site
  git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31

Changes take a couple of minutes to be propagated. You can verify whether they 
have been propagated by looking at the Last Published date at the bottom of 
http://hbase.apache.org/. It should match the date in the index.html on the 
asf-site branch in Git.

As a courtesy- reply-all to this email to let other committers know you pushed 
the site.



If failed, see https://builds.apache.org/job/hbase_generate_website/371/console

Re: Still Failing: HBase Generate Website

[stack]

Did you do the revert meantime Ted?

On Oct 8, 2016 19:01, "Ted Yu"  wrote:

> Logged INFRA-12731
>
> On Sat, Oct 8, 2016 at 6:56 PM, 张铎  wrote:
>
> > Build environment issue IS a issue. If we do not consider H0 and H1 as
> > broken, we need to fix the problem.
> >
> > And we are not sure if all other machines are OK right? As for now, the
> > failed machines wins, 2 vs. 1.
> >
> > Thanks.
> >
> > 2016-10-09 9:36 GMT+08:00 Ted Yu :
> >
> > > This seems to be build environment issue.
> > >
> > > Build #368 (green) was on H4 while #369 was on H0. #370 was on H1.
> > >
> > > On Sat, Oct 8, 2016 at 6:32 PM, 张铎  wrote:
> > >
> > > > This maybe related to a jruby issue.
> > > >
> > > > https://github.com/jruby/jruby/issues/2913
> > > >
> > > > It depends on the environment thus it may fail on some machines while
> > > > success on some other machines.
> > > >
> > > > 2016-10-09 9:29 GMT+08:00 Ted Yu :
> > > >
> > > > > This was the build 16750 went into:
> > > > >
> > > > > https://builds.apache.org/job/hbase_generate_website/368/
> > > > >
> > > > > which was green.
> > > > >
> > > > >
> > > > > On Sat, Oct 8, 2016 at 6:10 PM, Sean Busbey 
> > > wrote:
> > > > >
> > > > > > If the website can't build on the build machine then it can't
> > build.
> > > > > >
> > > > > > We've worked hard as a community to automate this stuff and I
> don't
> > > > want
> > > > > to
> > > > > > go backwards.
> > > > > >
> > > > > > --
> > > > > > Sean Busbey
> > > > > >
> > > > > > On Oct 8, 2016 14:48, "Ted Yu"  wrote:
> > > > > >
> > > > > > > I did a local build:
> > > > > > >
> > > > > > > Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> > > > > > > 2015-11-10T16:41:47+00:00)
> > > > > > > Maven home: /apache-maven-3.3.9
> > > > > > > Java version: 1.8.0_101, vendor: Oracle Corporation
> > > > > > > Java home: /jdk1.8.0_101/jre
> > > > > > > Default locale: en_US, platform encoding: UTF-8
> > > > > > > OS name: "linux", version: "3.10.0-327.28.2.el7.x86_64", arch:
> > > > "amd64",
> > > > > > > family: "unix"
> > > > > > >
> > > > > > > [INFO] Final Memory: 30M/1928M
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] Archetype project created in
> > > > > > > /hbase/hbase-archetypes/hbase-client-project/target/build-
> > > > > > > archetype/target/generated-sources/archetype
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] BUILD SUCCESS
> > > > > > > [INFO]
> > > > > > > 
> > > > > 
> > > > > > > [INFO] Total time: 3.168 s
> > > > > > >
> > > > > > > $ ls -l ./target/site/apache_hbase_reference_guide.pdf
> > > > > > > -rw-rw-r-- 1 hbase hbase 13535029 Oct  8 19:35
> > > > > > > ./target/site/apache_hbase_reference_guide.pdf
> > > > > > >
> > > > > > > I can attach the generated pdf to the JIRA if you want. It
> > contains
> > > > the
> > > > > > new
> > > > > > > guide on protobuf 3.
> > > > > > >
> > > > > > > The fstat error may be related to the build machine.
> > > > > > >
> > > > > > > Cheers
> > > > > > >
> > > > > > > On Sat, Oct 8, 2016 at 12:18 PM, Ted Yu 
> > > wrote:
> > > > > > >
> > > > > > > > This error didn't appear when the v1 was committed.
> > > > > > > >
> > > > > > > > Let me see if I can reproduce it locally on Linux.
> > > > > > > >
> > > > > > > > [ERROR] Failed to execute goal org.asciidoctor:asciidoctor-
> > > > > > > maven-plugin:1.5.3:process-asciidoc (output-pdf) on project
> > hbase:
> > > > > > > Execution output-pdf of goal org.asciidoctor:asciidoctor-
> > > > > > > maven-plugin:1.5.3:process-asciidoc failed:
> > org.jruby.exceptions.
> > > > > > RaiseException:
> > > > > > > (NotImplementedError) fstat unimplemented unsupported or native
> > > > support
> > > > > > > failed to load -> [Help 1]
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Oct 8, 2016 at 11:55 AM, Dima Spivak <
> > > > dimaspi...@apache.org>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Looks like HBASE-16750 again. Please revert this again, Ted,
> > and
> > > > > close
> > > > > > > as
> > > > > > > >> "won't fix" if we can't test it before pushing commits.
> > > > > > > >>
> > > > > > > >> On Saturday, October 8, 2016, Apache Jenkins Server <
> > > > > > > >> jenk...@builds.apache.org> wrote:
> > > > > > > >>
> > > > > > > >> > Build status: Still Failing
> > > > > > > >> >
> > > > > > > >> > If successful, the website and docs have been generated.
> To
> > > > update
> > > > > > the
> > > > > > > >> > live site, follow the instructions below. If failed, skip
> to
> > > the
> > > > > > > bottom
> > > > > > > >> of
> > > > > > > >> > this email.
> > > > > > > >> >
> > > > > >