[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16383689#comment-16383689
]
Misty Stanley-Jones commented on HBASE-20070:
-
-7 LGTM with code review (on Github) but I haven’t been able to test this
locally. It would be nice if someone did a test run before foisting this on
Jenkins. Remember the Jenkins job needs to be updated to run the script with
the new syntax too.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> HBASE-20070.5.patch, HBASE-20070.6.patch, HBASE-20070.7.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381430#comment-16381430
]
Misty Stanley-Jones commented on HBASE-20070:
-
Actually soft -1 on version 5. I forgot to mention that there is something
about the way you are adding files to git that is making it interactive (you
have to press {{q}} to get out of a pager). I didn't look into it to see what
the deal is but probably not appropriate for a Jenkins job.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> HBASE-20070.5.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381409#comment-16381409
]
Misty Stanley-Jones commented on HBASE-20070:
-
+1 on version 5.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> HBASE-20070.5.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381325#comment-16381325
]
Misty Stanley-Jones commented on HBASE-20070:
-
Testing latest patch now.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> HBASE-20070.5.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381162#comment-16381162
]
Misty Stanley-Jones commented on HBASE-20070:
-
FYI with that one change, I got a totally clean run of all phases including
adding the files, generating the patch, etc. I can't reproduce the dependency
problem you were seeing.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381149#comment-16381149
]
Misty Stanley-Jones commented on HBASE-20070:
-
You might be using {{cp}} from Homebrew. If it is in {{/usr/local/bin}} that's
probably what's going on. Yes, that's the line. I'm pretty sure that Linux
{{cp}} supporting {{-r}} is new so it is possible Jenkins won't work with this,
in which case you'll have to somehow check what flags are supported or just use
{{mv}} or something (even {{rsync}} but that's more complicated).
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1638#comment-1638
]
Misty Stanley-Jones commented on HBASE-20070:
-
-1 on patch 4, because it won't run on Mac out of the box, due to differences
in the {{cp}} command. I solved a similar thing with sed here:
[https://github.com/docker/docker.github.io/blob/master/_scripts/fetch-upstream-resources.sh#L10]
However it looks like Linux honors the {{-r}} flag for {{cp}} now, so maybe you
can just switch the {{-au}} to {{-r}} everywhere (after verifying on a Jenkins
worker that it has a version of {{cp}} that supports the flag?)
I've changed the {{cp}} locally and will do more testing today.
(I sent this hours ago but it didn't post because the session was expired but
the page doesn't have the smarts to realize that.)
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch, HBASE-20070.3.patch, HBASE-20070.4.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-15747) Fix illegal character in tablename in generated Maven site
[
https://issues.apache.org/jira/browse/HBASE-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379469#comment-16379469
]
Misty Stanley-Jones commented on HBASE-15747:
-
No, because that link referred to job 37, which has since aged off. Here is the
latest job:
[https://builds.apache.org/job/HBase%20Website%20Link%20Checker/138/artifact/link_report/warnX.html]
(search for {{illegal character}}).
> Fix illegal character in tablename in generated Maven site
> --
>
> Key: HBASE-15747
> URL: https://issues.apache.org/jira/browse/HBASE-15747
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Misty Stanley-Jones
>Priority: Trivial
> Labels: newbie
>
> See
> https://builds.apache.org/job/HBase%20Website%20Link%20Ckecker/37/artifact/link_report/warnX.html.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-20070:
Attachment: HBASE-20070-misty.patch.3
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070-misty.patch.3, HBASE-20070.0.patch, HBASE-20070.1.patch,
> HBASE-20070.2.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377609#comment-16377609
]
Misty Stanley-Jones commented on HBASE-20070:
-
No, adding the configuration to the reportsets in the POM didn't help either.
:/ I am confused, but need to step away from this for a bit. I'll attach my
patch as it currently stands, for your review. I didn't try to normalize to
your patch yet, so ignore any changes you incorporated already.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch, HBASE-20070.2.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377569#comment-16377569
]
Misty Stanley-Jones commented on HBASE-20070:
-
I'm confused why the Javadoc is failing even with this in the POM:
{code:java}
-Xdoclint:none
{code}
I found that referred to at
[http://www.locked.de/2015/04/05/how-to-ignore-maven-javadoc-errors-in-java-8/.|http://www.locked.de/2015/04/05/how-to-ignore-maven-javadoc-errors-in-java-8/]
But I think that maybe the configuration clause is actually in the wrong place
in the POM. I'm testing this assumption now.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch, HBASE-20070.2.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377537#comment-16377537
]
Misty Stanley-Jones commented on HBASE-20070:
-
I think maybe we aren't supposed to be doing {{mvn clean site}} after doing the
install? Maybe just {{mvn site}}. This might be the cause of the Javadoc errors
you're seeing. I'm testing locally now.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch, HBASE-20070.2.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377516#comment-16377516
]
Misty Stanley-Jones commented on HBASE-20070:
-
A little bit of feedback on your patches so far. Some of this may be me not
understanding certain ways of doing things in Bash, so forgive me if so.
{code:java}
if [ "${PUSHED}" -ne 0 ]; then
echo "$CURRENT_HBASE_COMMIT is already mentioned in the hbase-site commit log.
Not building."
exit 0
else{code}
I think this might not be quite right (mine was also probably wrong). If I am
understanding this correctly, this will pass if the hash is in any branch we
know about, not just `master`, but I think we only care if it is in `master`.
Can we narrow it down more? I'm also not in love with this indent-less syntax
for the if contents.
I think we need to document that the stuff that removes {{~/.m2}} may not work
locally but that's specifically to try to avoid Jenkins server problems so it
can probably be ignored locally. In fact maybe there is some cleverer way for
us to sandbox ourselves, but I am not a Maven expert.
I think maybe we need to add a {{–push=true}} or similar flag to this script so
we can do local tests without it always pushing the new site.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch, HBASE-20070.2.patch,
> hbase-install-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377493#comment-16377493
]
Misty Stanley-Jones commented on HBASE-20070:
-
Yeah it is still needed because that is stuff that is actually checked in but
we want to nuke and pave it.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377490#comment-16377490
]
Misty Stanley-Jones commented on HBASE-20070:
-
{code:java}
> index 06d160a64c..4628697c5f 100644
36c40
< +if [ -z "$CURRENT_HBASE_COMMIT "]; then
---
> +if [ -z "$CURRENT_HBASE_COMMIT" ]; then
55c59
< +PUSHED=$(git log -pretty=%H | grep ${CURRENT_HBASE_COMMIT})
---
> +PUSHED=$(git log --pretty=%H | grep ${CURRENT_HBASE_COMMIT}){code}
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-20070:
Attachment: HBASE-20070-misty.patch.1
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377473#comment-16377473
]
Misty Stanley-Jones commented on HBASE-20070:
-
Attached another version of mine with a couple fixes I noticed in testing.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070-misty.patch.1,
> HBASE-20070.0.patch, HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377430#comment-16377430
]
Misty Stanley-Jones commented on HBASE-20070:
-
I think that build failure is unrelated and probably a `git bisect` is needed
to see who broke it.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070.0.patch,
> HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377425#comment-16377425
]
Misty Stanley-Jones commented on HBASE-20070:
-
I don't think you can do absolutely everything with plumbing commands. Not 100%
sure though.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070.0.patch,
> HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377410#comment-16377410
]
Misty Stanley-Jones commented on HBASE-20070:
-
I'll look at your patch if you look at mine. :)
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070.0.patch,
> HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-20070:
Attachment: HBASE-20070-misty.patch
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Attachments: HBASE-20070-misty.patch, HBASE-20070.0.patch,
> HBASE-20070.1.patch,
> hbase-build-log-a29b3caf4dbc7b8833474ef5da5438f7f6907e00.txt
>
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20070) website generation is failing
[
https://issues.apache.org/jira/browse/HBASE-20070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377341#comment-16377341
]
Misty Stanley-Jones commented on HBASE-20070:
-
I'm taking a look now.
> website generation is failing
> -
>
> Key: HBASE-20070
> URL: https://issues.apache.org/jira/browse/HBASE-20070
> Project: HBase
> Issue Type: Bug
> Components: website
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
>
> website generation has been failing since Feb 20th
> {code}
> Checking out files: 100% (68971/68971), done.
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> PUSHED is 2
> is not yet mentioned in the hbase-site commit log. Assuming we don't have it
> yet. 2
> Building HBase
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
> support was removed in 8.0
> Failure: mvn clean site
> Build step 'Execute shell' marked build as failure
> {code}
> The status email says
> {code}
> Build status: Still Failing
> The HBase website has not been updated to incorporate HBase commit
> ${CURRENT_HBASE_COMMIT}.
> {code}
> Looking at the code where that grep happens, it looks like the env variable
> CURRENT_HBASE_COMMIT isn't getting set. That comes from some git command. I'm
> guessing the version of git changed on the build hosts and upended our
> assumptions.
> we should fix this to 1) rely on git's porcelain interface, and 2) fail as
> soon as that git command fails
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-18974) Document "Becoming a Committer"
[ https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257425#comment-16257425 ] Misty Stanley-Jones commented on HBASE-18974: - The Hadoop QA error is because my patch needs to be applied on top of yours and then squashed. > Document "Becoming a Committer" > --- > > Key: HBASE-18974 > URL: https://issues.apache.org/jira/browse/HBASE-18974 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18974-copyedit-addendum.patch, HBASE-18974.patch, > HBASE-18974.v2.patch, HBASE-18974.v3.patch > > > Based on the mailing list discussion at > https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E > it sounds like we should record some of the thoughts for future contributors > to refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18974) Document "Becoming a Committer"
[ https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257419#comment-16257419 ] Misty Stanley-Jones commented on HBASE-18974: - I built with my updates and it looks good to me locally. Be aware that the links to top-level site pages won't work on the local build, but this is known. > Document "Becoming a Committer" > --- > > Key: HBASE-18974 > URL: https://issues.apache.org/jira/browse/HBASE-18974 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18974-copyedit-addendum.patch, HBASE-18974.patch, > HBASE-18974.v2.patch, HBASE-18974.v3.patch > > > Based on the mailing list discussion at > https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E > it sounds like we should record some of the thoughts for future contributors > to refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18974) Document "Becoming a Committer"
[ https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-18974: Attachment: HBASE-18974-copyedit-addendum.patch I kind of kept copyediting for a few sections after your changes. You can revert those lines if you feel like it's not necessary. Building locally to test now but wanted to get this to you. I'll amend and re-attach if it breaks anything. > Document "Becoming a Committer" > --- > > Key: HBASE-18974 > URL: https://issues.apache.org/jira/browse/HBASE-18974 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18974-copyedit-addendum.patch, HBASE-18974.patch, > HBASE-18974.v2.patch, HBASE-18974.v3.patch > > > Based on the mailing list discussion at > https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E > it sounds like we should record some of the thoughts for future contributors > to refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18974) Document "Becoming a Committer"
[ https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254097#comment-16254097 ] Misty Stanley-Jones commented on HBASE-18974: - Yes, I do! Sorry for the delay. I'll try to get to it today. > Document "Becoming a Committer" > --- > > Key: HBASE-18974 > URL: https://issues.apache.org/jira/browse/HBASE-18974 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18974.patch, HBASE-18974.v2.patch, > HBASE-18974.v3.patch > > > Based on the mailing list discussion at > https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E > it sounds like we should record some of the thoughts for future contributors > to refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18974) Document "Becoming a Committer"
[ https://issues.apache.org/jira/browse/HBASE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240603#comment-16240603 ] Misty Stanley-Jones commented on HBASE-18974: - I'll take a look and attach a copyedit patch which you can apply and squash if you like. > Document "Becoming a Committer" > --- > > Key: HBASE-18974 > URL: https://issues.apache.org/jira/browse/HBASE-18974 > Project: HBase > Issue Type: Bug > Components: community, documentation >Reporter: Mike Drob >Assignee: Mike Drob > Attachments: HBASE-18974.patch, HBASE-18974.v2.patch > > > Based on the mailing list discussion at > https://lists.apache.org/thread.html/81c633cbe1f6f78421cbdad5b9549643c67803a723a9d86a513264c0@%3Cdev.hbase.apache.org%3E > it sounds like we should record some of the thoughts for future contributors > to refer to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219460#comment-16219460
]
Misty Stanley-Jones commented on HBASE-15753:
-
Yeah, you still have to do
{code:java}
mvn install
{code}
before you can build the docs for the first time. I thought we fixed this.
Anyway after I do
{code:java}
mvn install
{code}
I am able to build the docs with just
{code:java}
mvn site -DskipTests
{code}
and no errors.
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219076#comment-16219076
]
Misty Stanley-Jones edited comment on HBASE-15753 at 10/25/17 5:01 PM:
---
The error I get is:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
hbase: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin:
Failed to execute goal on project hbase-server: Could not resolve dependencies
for project org.apache.hbase:hbase-server:jar:3.0.0-SNAPSHOT: The following
artifacts could not be resolved:
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT,
org.apache.hbase:hbase-http:jar:tests:3.0.0-SNAPSHOT: Could not find artifact
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT in project.local
(file:/Users/misty/repos/asf/hbase/hbase-server/src/site/resources/repo) ->
[Help 1]
[ERROR]
{code}
I think this is actually unrelated to this JIRA. :/
was (Author: misty):
The error I get is:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
hbase: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin:
Failed to execute goal on project hbase-server: Could not resolve dependencies
for project org.apache.hbase:hbase-server:jar:3.0.0-SNAPSHOT: The following
artifacts could not be resolved:
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT,
org.apache.hbase:hbase-http:jar:tests:3.0.0-SNAPSHOT: Could not find artifact
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT in project.local
(file:/Users/misty/repos/asf/hbase/hbase-server/src/site/resources/repo) ->
[Help 1]
[ERROR]
{code}
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219077#comment-16219077
]
Misty Stanley-Jones commented on HBASE-15753:
-
It seems counter-intuitive that we'd need to skip the Javadoc when we are
specifically building docs (which includes Javadoc).
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219076#comment-16219076
]
Misty Stanley-Jones commented on HBASE-15753:
-
The error I get is:
{code:java}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
hbase: failed to get report for org.apache.maven.plugins:maven-javadoc-plugin:
Failed to execute goal on project hbase-server: Could not resolve dependencies
for project org.apache.hbase:hbase-server:jar:3.0.0-SNAPSHOT: The following
artifacts could not be resolved:
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT,
org.apache.hbase:hbase-http:jar:tests:3.0.0-SNAPSHOT: Could not find artifact
org.apache.hbase:hbase-http:jar:3.0.0-SNAPSHOT in project.local
(file:/Users/misty/repos/asf/hbase/hbase-server/src/site/resources/repo) ->
[Help 1]
[ERROR]
{code}
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (HBASE-15753) Site does not build with the instructions in the book
[
https://issues.apache.org/jira/browse/HBASE-15753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones reassigned HBASE-15753:
---
Assignee: Misty Stanley-Jones
> Site does not build with the instructions in the book
> -
>
> Key: HBASE-15753
> URL: https://issues.apache.org/jira/browse/HBASE-15753
> Project: HBase
> Issue Type: Bug
> Components: community, documentation, website
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
>
> Originally reported by [~clarax98007] in HBASE-15337.
> Instructions in the book say to run:
> {code}
> mvn site -DskipTests
> {code}
> But it fails with javadoc related errors.
> Seems that we are using this in the jenkins job that [~misty] had setup
> (https://builds.apache.org/job/hbase_generate_website/):
> {code}mvn site -DskipTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
> -Dfindbugs.skip=true {code}
> We should either fix the javadoc, or update the instructions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check
[
https://issues.apache.org/jira/browse/HBASE-19042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211469#comment-16211469
]
Misty Stanley-Jones commented on HBASE-19042:
-
I'm looking into this too.
> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Peter Somogyi
>Assignee: Misty Stanley-Jones
>Priority: Blocker
> Attachments: Dockerfile, HBASE-19042-v1.patch, HBASE-19042-v10.patch,
> HBASE-19042-v11.patch, HBASE-19042-v12.patch, HBASE-19042-v2.patch,
> HBASE-19042-v3.patch, HBASE-19042-v4.patch, HBASE-19042-v5.patch,
> HBASE-19042-v6.patch, HBASE-19042-v7.patch, HBASE-19042-v8.patch,
> HBASE-19042-v9.patch, HBASE-19042.patch
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 [91mNo /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 [0m[91m--2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)...
> [0m[91m23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 [0m[91mResolving edelivery.oracle.com (edelivery.oracle.com)...
> [0m[91m23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com
> (edelivery.oracle.com)|23.39.16.136|:443... [0m[91mconnected.
> 06:45:14 [0m[91mHTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14
> 06:45:14 [0m[91mdownload failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 [0m[91mdpkg: error processing package oracle-java8-installer
> (--configure):
> 06:45:14 subprocess installed post-installation script returned error exit
> status 1
> 06:45:14 [0m[91mErrors were encountered while processing:
> 06:45:14 oracle-java8-installer
> 06:45:29 [0m[91mE: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 [0mThe command '/bin/sh -c apt-get -q update && apt-get -q install
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code:
> 100
> 06:45:29
> 06:45:29 Total Elapsed time: 3m 19s
> 06:45:29
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|'
> oracle-java8-installer.*
> sudo sed -i
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
> oracle-java8-installer.*
> sudo sed -i
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
> oracle-java8-installer.*
> sudo sed -i 's|J_DIR=jdk1.8.0_144|J_DIR=jdk1.8.0_152|'
> oracle-java8-installer.*
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check
[
https://issues.apache.org/jira/browse/HBASE-19042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16210461#comment-16210461
]
Misty Stanley-Jones commented on HBASE-19042:
-
It actually intentionally pegs the Maven version, and you'd need to change the
{{FROM}} line to move to a different Maven version.
> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Peter Somogyi
>Priority: Blocker
> Attachments: Dockerfile
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 [91mNo /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 [0m[91m--2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)...
> [0m[91m23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 [0m[91mResolving edelivery.oracle.com (edelivery.oracle.com)...
> [0m[91m23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com
> (edelivery.oracle.com)|23.39.16.136|:443... [0m[91mconnected.
> 06:45:14 [0m[91mHTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14
> 06:45:14 [0m[91mdownload failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 [0m[91mdpkg: error processing package oracle-java8-installer
> (--configure):
> 06:45:14 subprocess installed post-installation script returned error exit
> status 1
> 06:45:14 [0m[91mErrors were encountered while processing:
> 06:45:14 oracle-java8-installer
> 06:45:29 [0m[91mE: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 [0mThe command '/bin/sh -c apt-get -q update && apt-get -q install
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code:
> 100
> 06:45:29
> 06:45:29 Total Elapsed time: 3m 19s
> 06:45:29
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|'
> oracle-java8-installer.*
> sudo sed -i
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
> oracle-java8-installer.*
> sudo sed -i
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
> oracle-java8-installer.*
> sudo sed -i 's|J_DIR=jdk1.8.0_144|J_DIR=jdk1.8.0_152|'
> oracle-java8-installer.*
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19042) Oracle Java 8u144 downloader broken in precommit check
[
https://issues.apache.org/jira/browse/HBASE-19042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-19042:
Attachment: Dockerfile
It is definitely possible that this could be improved, but here's a start.
> Oracle Java 8u144 downloader broken in precommit check
> --
>
> Key: HBASE-19042
> URL: https://issues.apache.org/jira/browse/HBASE-19042
> Project: HBase
> Issue Type: Bug
> Components: build
>Reporter: Peter Somogyi
>Priority: Blocker
> Attachments: Dockerfile
>
>
> Precommit job fails to install Oracle Java 8 to docker image which is due to
> Oracle's new Java version, 8u151.
> As this thread point out we probably need to upgrade to latest java 8
> version: https://ubuntuforums.org/showthread.php?t=2374686
> {code}
> 06:45:14 Setting up java-common (0.51) ...
> 06:45:14 Setting up oracle-java8-installer (8u144-1~webupd8~0) ...
> 06:45:14 [91mNo /var/cache/oracle-jdk8-installer/wgetrc file found.
> 06:45:14 Creating /var/cache/oracle-jdk8-installer/wgetrc and
> 06:45:14 using default oracle-java8-installer wgetrc settings for it.
> 06:45:14 Downloading Oracle Java 8...
> 06:45:14 [0m[91m--2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 Resolving download.oracle.com (download.oracle.com)...
> [0m[91m23.59.189.81, 23.59.189.91
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> https://edelivery.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz
> 06:45:14 [0m[91mResolving edelivery.oracle.com (edelivery.oracle.com)...
> [0m[91m23.39.16.136, 2600:1409:a:39e::2d3e, 2600:1409:a:39c::2d3e
> 06:45:14 Connecting to edelivery.oracle.com
> (edelivery.oracle.com)|23.39.16.136|:443... [0m[91mconnected.
> 06:45:14 [0m[91mHTTP request sent, awaiting response... [0m[91m302 Moved
> Temporarily
> 06:45:14 Location:
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> [following]
> 06:45:14 --2017-10-18 13:45:14--
> http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-linux-x64.tar.gz?AuthParam=1508334434_7da3c9610b0368a45f954cd47d91121c
> 06:45:14 Connecting to download.oracle.com
> (download.oracle.com)|23.59.189.81|:80... [0m[91mconnected.
> 06:45:14 HTTP request sent, awaiting response... [0m[91m404 Not Found
> 06:45:14 2017-10-18 13:45:14 ERROR 404: Not Found.
> 06:45:14
> 06:45:14 [0m[91mdownload failed
> 06:45:14 Oracle JDK 8 is NOT installed.
> 06:45:14 [0m[91mdpkg: error processing package oracle-java8-installer
> (--configure):
> 06:45:14 subprocess installed post-installation script returned error exit
> status 1
> 06:45:14 [0m[91mErrors were encountered while processing:
> 06:45:14 oracle-java8-installer
> 06:45:29 [0m[91mE: Sub-process /usr/bin/dpkg returned an error code (1)
> 06:45:29 [0mThe command '/bin/sh -c apt-get -q update && apt-get -q install
> --no-install-recommends -y oracle-java8-installer' returned a non-zero code:
> 100
> 06:45:29
> 06:45:29 Total Elapsed time: 3m 19s
> 06:45:29
> 06:45:29 ERROR: Docker failed to build image.
> {code}
> Workaround mentioned in the forum post:
> {code}
> sudo sed -i 's|JAVA_VERSION=8u144|JAVA_VERSION=8u152|'
> oracle-java8-installer.*
> sudo sed -i
> 's|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/|PARTNER_URL=http://download.oracle.com/otn-pub/java/jdk/8u152-b16/aa0333dd3019491ca4f6ddbe78cdb6d0/|'
> oracle-java8-installer.*
> sudo sed -i
> 's|SHA256SUM_TGZ="e8a341ce566f32c3d06f6d0f0eeea9a0f434f538d22af949ae58bc86f2eeaae4"|SHA256SUM_TGZ="218b3b340c3f6d05d940b817d0270dfe0cfd657a636bad074dcabe0c111961bf"|'
> oracle-java8-installer.*
> sudo sed -i 's|J_DIR=jdk1.8.0_144|J_DIR=jdk1.8.0_152|'
> oracle-java8-installer.*
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-17823: Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) Release Note: HBase now uses stability and audience annotations sourced from Apache Yetus, instead of the custom annotations that were previously in place. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-17823.0.patch, HBASE-17823.1.patch, > HBASE-17823.2.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16161820#comment-16161820 ] Misty Stanley-Jones commented on HBASE-17823: - v2 LGTM! Docs are more clear. Thank you! > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0-alpha-3 > > Attachments: HBASE-17823.0.patch, HBASE-17823.1.patch, > HBASE-17823.2.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-18635:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
> Fix asciidoc warnings
> -
>
> Key: HBASE-18635
> URL: https://issues.apache.org/jira/browse/HBASE-18635
> Project: HBase
> Issue Type: Bug
>Reporter: Misty Stanley-Jones
>Assignee: Jan Hentschel
> Fix For: 3.0.0
>
> Attachments: HBASE-18635.master.001.patch,
> HBASE-18635.master.002.patch
>
>
> When building docs, I noticed:
> {code}
> Failed to parse formatted text: To supply filters to the Scanner object or
> configure the Scanner in any other way, you can create a text file and add
> your filter to the file. For example, to return only rows for which keys
> start with codephu123/codeph and use a batch size of 100, the
> filter file would look like this:
> Scanner batch="100" filter { "type": "PrefixFilter",
> "value": "u123" } /filter /Scanner
> {code}
> Working hypthesis is that we should either be using proper codeblocks rather
> than pre tags. Otherwise we may need to do something to escape curly braces.
> Asciidoctor is probably trying to interpret them as Liquid tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142111#comment-16142111
]
Misty Stanley-Jones commented on HBASE-18635:
-
I just tested it out and it looks great! I'll go ahead and push it to `master`.
Thanks!
> Fix asciidoc warnings
> -
>
> Key: HBASE-18635
> URL: https://issues.apache.org/jira/browse/HBASE-18635
> Project: HBase
> Issue Type: Bug
>Reporter: Misty Stanley-Jones
>Assignee: Jan Hentschel
> Attachments: HBASE-18635.master.001.patch,
> HBASE-18635.master.002.patch
>
>
> When building docs, I noticed:
> {code}
> Failed to parse formatted text: To supply filters to the Scanner object or
> configure the Scanner in any other way, you can create a text file and add
> your filter to the file. For example, to return only rows for which keys
> start with codephu123/codeph and use a batch size of 100, the
> filter file would look like this:
> Scanner batch="100" filter { "type": "PrefixFilter",
> "value": "u123" } /filter /Scanner
> {code}
> Working hypthesis is that we should either be using proper codeblocks rather
> than pre tags. Otherwise we may need to do something to escape curly braces.
> Asciidoctor is probably trying to interpret them as Liquid tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135452#comment-16135452
]
Misty Stanley-Jones commented on HBASE-18635:
-
While you're in there, can you fix:
{code}
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1116: section title
out of sequence: expected level 2, got level 3
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1132: section title
out of sequence: expected level 2, got level 3
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1143: section title
out of sequence: expected level 2, got level 3
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1152: section title
out of sequence: expected level 2, got level 3
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1190: section title
out of sequence: expected level 2, got level 3
asciidoctor: WARNING: _chapters/schema_design.adoc: line 1199: section title
out of sequence: expected level 2, got level 3
{code}
Looks like some heading levels are out of sequence.
> Fix asciidoc warnings
> -
>
> Key: HBASE-18635
> URL: https://issues.apache.org/jira/browse/HBASE-18635
> Project: HBase
> Issue Type: Bug
>Reporter: Misty Stanley-Jones
>Assignee: Jan Hentschel
> Attachments: HBASE-18635.master.001.patch
>
>
> When building docs, I noticed:
> {code}
> Failed to parse formatted text: To supply filters to the Scanner object or
> configure the Scanner in any other way, you can create a text file and add
> your filter to the file. For example, to return only rows for which keys
> start with codephu123/codeph and use a batch size of 100, the
> filter file would look like this:
> Scanner batch="100" filter { "type": "PrefixFilter",
> "value": "u123" } /filter /Scanner
> {code}
> Working hypthesis is that we should either be using proper codeblocks rather
> than pre tags. Otherwise we may need to do something to escape curly braces.
> Asciidoctor is probably trying to interpret them as Liquid tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134526#comment-16134526 ] Misty Stanley-Jones commented on HBASE-17823: - That would work, or just keep the doc changes in a separate commit during PR review (you can review each commit separately) and then squash them before push. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134205#comment-16134205 ] Misty Stanley-Jones commented on HBASE-17823: - It builds and I don't see any problems. If you'd like to work together on the doc changes, can you just open a Github PR and tag me there so I can commit into it? > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18635) Fix asciidoc warnings
[
https://issues.apache.org/jira/browse/HBASE-18635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134198#comment-16134198
]
Misty Stanley-Jones commented on HBASE-18635:
-
It's in src/main/asciidoc/_chapters/external_apis.adoc
> Fix asciidoc warnings
> -
>
> Key: HBASE-18635
> URL: https://issues.apache.org/jira/browse/HBASE-18635
> Project: HBase
> Issue Type: Bug
>Reporter: Misty Stanley-Jones
>
> When building docs, I noticed:
> {code}
> Failed to parse formatted text: To supply filters to the Scanner object or
> configure the Scanner in any other way, you can create a text file and add
> your filter to the file. For example, to return only rows for which keys
> start with codephu123/codeph and use a batch size of 100, the
> filter file would look like this:
> Scanner batch="100" filter { "type": "PrefixFilter",
> "value": "u123" } /filter /Scanner
> {code}
> Working hypthesis is that we should either be using proper codeblocks rather
> than pre tags. Otherwise we may need to do something to escape curly braces.
> Asciidoctor is probably trying to interpret them as Liquid tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-18635) Fix asciidoc warnings
Misty Stanley-Jones created HBASE-18635:
---
Summary: Fix asciidoc warnings
Key: HBASE-18635
URL: https://issues.apache.org/jira/browse/HBASE-18635
Project: HBase
Issue Type: Bug
Reporter: Misty Stanley-Jones
When building docs, I noticed:
{code}
Failed to parse formatted text: To supply filters to the Scanner object or
configure the Scanner in any other way, you can create a text file and add your
filter to the file. For example, to return only rows for which keys start with
codephu123/codeph and use a batch size of 100, the filter file
would look like this:
Scanner batch="100" filter { "type": "PrefixFilter",
"value": "u123" } /filter /Scanner
{code}
Working hypthesis is that we should either be using proper codeblocks rather
than pre tags. Otherwise we may need to do something to escape curly braces.
Asciidoctor is probably trying to interpret them as Liquid tags.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-17823) Migrate to Apache Yetus Audience Annotations
[ https://issues.apache.org/jira/browse/HBASE-17823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134190#comment-16134190 ] Misty Stanley-Jones commented on HBASE-17823: - Please have a look at http://hbase.apache.org/book.html#hbase.client.api.surface and make sure nothing needs changing due to this. > Migrate to Apache Yetus Audience Annotations > > > Key: HBASE-17823 > URL: https://issues.apache.org/jira/browse/HBASE-17823 > Project: HBase > Issue Type: Improvement > Components: API >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Sean Busbey > Fix For: 2.0.0 > > Attachments: HBASE-17823.0.patch > > > Migrate from our own audience annotation handling to apache yetus' > implementation. > [discussion thread on > dev@hbase|https://lists.apache.org/thread.html/5a83d37c9c763b3fc4114231489a073167ac69dbade9774af5ca4fb4@%3Cdev.hbase.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-14785) Hamburger menu for mobile site
[
https://issues.apache.org/jira/browse/HBASE-14785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134179#comment-16134179
]
Misty Stanley-Jones commented on HBASE-14785:
-
I'm a little concerned about "sometimes" -- it's not happening every time?
As a working hypothesis, there is probably some time where {{project.basedir}}
is referred to in the POM with slightly off syntax and isn't getting expanded.
> Hamburger menu for mobile site
> --
>
> Key: HBASE-14785
> URL: https://issues.apache.org/jira/browse/HBASE-14785
> Project: HBase
> Issue Type: Sub-task
> Components: website
>Affects Versions: 2.0.0
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments:
> 0001-HBASE-14774-Addendum-Exclude-src-main-site-resources.patch,
> HBASE-14774-addendum2_tweak_css.patch, HBASE-14785-addendum.patch,
> HBASE-14785-addendum-v1.patch, HBASE-14785.patch, HBASE-14785-v1.patch,
> HBASE-14785-v2.patch, maven-fluido-skin-1.5-HBASE.jar
>
>
> Figure out how to do a hamburger menu on mobile.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122508#comment-16122508 ] Misty Stanley-Jones commented on HBASE-18548: - Jenkins jobs have been converted. > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122410#comment-16122410 ] Misty Stanley-Jones commented on HBASE-18548: - It was a fault with the Jenkins job, not this. I've fixed it and babysitting the Jenkins job now. I'll convert the link checker Jenkins job next. > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-18548: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the review! Pushed to `master`. > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-18548: Status: Patch Available (was: Open) > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120695#comment-16120695 ] Misty Stanley-Jones commented on HBASE-18548: - Assuming this gets approved and merged, I'll update the Jenkins jobs to use the scripts directly. > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18548) Move sources of important Jenkins jobs into source control
[ https://issues.apache.org/jira/browse/HBASE-18548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-18548: Attachment: HBASE-18548.patch Patch includes the two scripts and some updated docs about how to generate the site. > Move sources of important Jenkins jobs into source control > -- > > Key: HBASE-18548 > URL: https://issues.apache.org/jira/browse/HBASE-18548 > Project: HBase > Issue Type: Bug > Components: documentation, scripts >Affects Versions: 2.0.0-alpha-1 >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18548.patch > > > Move sources of the following Jenkins jobs into source control: > https://builds.apache.org/job/hbase_generate_website/ > https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18548) Move sources of important Jenkins jobs into source control
Misty Stanley-Jones created HBASE-18548: --- Summary: Move sources of important Jenkins jobs into source control Key: HBASE-18548 URL: https://issues.apache.org/jira/browse/HBASE-18548 Project: HBase Issue Type: Bug Components: documentation, scripts Affects Versions: 2.0.0-alpha-1 Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones Priority: Critical Fix For: 2.0.0 Move sources of the following Jenkins jobs into source control: https://builds.apache.org/job/hbase_generate_website/ https://builds.apache.org/view/All/job/HBase%20Website%20Link%20Checker/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
[
https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16113447#comment-16113447
]
Misty Stanley-Jones commented on HBASE-15042:
-
Unless I'm confused, you don't need to change anything, because the website
gets built into the {{target/}} directory, and doesn't care about {{src/}} at
all, assuming that Maven can find what it needs.
> refactor so that site materials are in the Standard Maven Place
> ---
>
> Key: HBASE-15042
> URL: https://issues.apache.org/jira/browse/HBASE-15042
> Project: HBase
> Issue Type: Task
> Components: build, website
>Reporter: Sean Busbey
>Assignee: Jan Hentschel
>Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-15042.master.001.patch,
> HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}}
> rather than the maven prescribed {{src/site}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18430) Typo in "contributing to documentation" page
[
https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096860#comment-16096860
]
Misty Stanley-Jones commented on HBASE-18430:
-
No worries. The sign-off is not a HBase requirement, just a personal preference
for some of us. It just adds that little "Signed-off by" line to the commit
message. It's actually something that happens during the {{git commit}}, not
the {{git format-patch}}. Your {{git format-patch}} is perfect. If you commit
and then realize you didn't sign off, you can do {{git commit --amend -s}}. I
do that all the time. :) You can always look at your existing commit by doing
{{git log -n1}}.
> Typo in "contributing to documentation" page
>
>
> Key: HBASE-18430
> URL: https://issues.apache.org/jira/browse/HBASE-18430
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Coral
>Assignee: Coral
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18430.patch
>
>
> Be sure to set the component to Documentation in addition any other involved
> components.
> Missing "to." Should be:
> Be sure to set the component to Documentation in addition *to* any other
> involved components.
> http://hbase.apache.org/book.html#appendix_contributing_to_documentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18430) Typo in "contributing to documentation" page
[
https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-18430:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0-alpha-2
3.0.0
Release Note: Pushed to {{master}}. Thanks, Coral! Congratulations on your
first Apache HBase commit!
Status: Resolved (was: Patch Available)
> Typo in "contributing to documentation" page
>
>
> Key: HBASE-18430
> URL: https://issues.apache.org/jira/browse/HBASE-18430
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Coral
>Assignee: Coral
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18430.patch
>
>
> Be sure to set the component to Documentation in addition any other involved
> components.
> Missing "to." Should be:
> Be sure to set the component to Documentation in addition *to* any other
> involved components.
> http://hbase.apache.org/book.html#appendix_contributing_to_documentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18430) Typo in "contributing to documentation" page
[ https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096828#comment-16096828 ] Misty Stanley-Jones commented on HBASE-18430: - With that having been said, this LGTM and I will commit it. Thanks [~coral.w]! > Typo in "contributing to documentation" page > > > Key: HBASE-18430 > URL: https://issues.apache.org/jira/browse/HBASE-18430 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Coral >Assignee: Coral > Attachments: HBASE-18430.patch > > > Be sure to set the component to Documentation in addition any other involved > components. > Missing "to." Should be: > Be sure to set the component to Documentation in addition *to* any other > involved components. > http://hbase.apache.org/book.html#appendix_contributing_to_documentation -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18430) Typo in "contributing to documentation" page
[
https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096826#comment-16096826
]
Misty Stanley-Jones commented on HBASE-18430:
-
No, {{-s}} is not cryptographic signing. You use {{-S}} for that. Gotta love
{{git}}. I didn't realize that about the subject. I don't recall seeing it in
other patches created using {{git format-patch}}, but when I look back at my
old patches it is there. Sorry about that!
The {{-s}} is useful for committers who are committing others' patches. It adds
a sign-off line for you beneath the sign-off line for the contributor. It's not
a current requirement, and I forget to do it half the time myself.
> Typo in "contributing to documentation" page
>
>
> Key: HBASE-18430
> URL: https://issues.apache.org/jira/browse/HBASE-18430
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Coral
>Assignee: Coral
> Attachments: HBASE-18430.patch
>
>
> Be sure to set the component to Documentation in addition any other involved
> components.
> Missing "to." Should be:
> Be sure to set the component to Documentation in addition *to* any other
> involved components.
> http://hbase.apache.org/book.html#appendix_contributing_to_documentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18430) Typo in "contributing to documentation" page
[
https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096810#comment-16096810
]
Misty Stanley-Jones commented on HBASE-18430:
-
Looks great. Please amend the commit message to remove the {{[patch]}} prefix,
as we don't use that. Also consider signing your commit by adding the {{-s}}
flag to the git commit message. To do both things at once, do a command like:
{code}
git commit --amend -s
{code}
> Typo in "contributing to documentation" page
>
>
> Key: HBASE-18430
> URL: https://issues.apache.org/jira/browse/HBASE-18430
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Coral
>Assignee: Coral
> Attachments: HBASE-18430.patch
>
>
> Be sure to set the component to Documentation in addition any other involved
> components.
> Missing "to." Should be:
> Be sure to set the component to Documentation in addition *to* any other
> involved components.
> http://hbase.apache.org/book.html#appendix_contributing_to_documentation
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18430) Typo in "contributing to documentation
[ https://issues.apache.org/jira/browse/HBASE-18430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16096697#comment-16096697 ] Misty Stanley-Jones commented on HBASE-18430: - Hi [~coral.w]! Please shout out if you need any help on this or when you'd like a review. Thanks! > Typo in "contributing to documentation > -- > > Key: HBASE-18430 > URL: https://issues.apache.org/jira/browse/HBASE-18430 > Project: HBase > Issue Type: Bug > Components: documentation >Reporter: Coral >Assignee: Coral > > Be sure to set the component to Documentation in addition any other involved > components. > Missing "to." Should be: > Be sure to set the component to Documentation in addition *to* any other > involved components. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-18332:
Resolution: Fixed
Hadoop Flags: Reviewed
Release Note: Committed to master and branch-2. Thanks!
Status: Resolved (was: Patch Available)
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch,
> HBASE-18332.master.002.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090983#comment-16090983
]
Misty Stanley-Jones commented on HBASE-18332:
-
LGTM! I'll commit.
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch,
> HBASE-18332.master.002.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16088021#comment-16088021
]
Misty Stanley-Jones commented on HBASE-18332:
-
The HTML looks great. I believe the PDF has a regression that the logo image no
longer shows up on the first page. It's not an urgent issue but it's not a
regression I'm happy with. Can you look into it?
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087868#comment-16087868
]
Misty Stanley-Jones commented on HBASE-18332:
-
By the way, we don't use the Change ID, so you might want to modify your Git
set-up so that it doesn't get added to commit messages in your HBase repo.
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18332) Upgrade asciidoctor-maven-plugin
[
https://issues.apache.org/jira/browse/HBASE-18332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087864#comment-16087864
]
Misty Stanley-Jones commented on HBASE-18332:
-
Let me try building the docs with this patch. Thanks [~psomogyi]
> Upgrade asciidoctor-maven-plugin
>
>
> Key: HBASE-18332
> URL: https://issues.apache.org/jira/browse/HBASE-18332
> Project: HBase
> Issue Type: Improvement
> Components: site
>Reporter: Peter Somogyi
>Assignee: Peter Somogyi
>Priority: Minor
> Fix For: 3.0.0, 2.0.0-alpha-2
>
> Attachments: HBASE-18332.master.001.patch
>
>
> HBASE-18264 upgraded asciidoctor-maven-plugin and asciidoctorj-pdf but it
> caused build failure for {{site}} goal due to a change in pdfmark generation.
> These plugins were rolled back in HBASE-18320.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063259#comment-16063259 ] Misty Stanley-Jones edited comment on HBASE-12794 at 6/26/17 3:32 PM: -- Committed to master and branch-2 (same patch). was (Author: misty): Committed to master. Unsure if I need to cherry-pick this somewhere else. It's docs so I guess not? > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063259#comment-16063259 ] Misty Stanley-Jones commented on HBASE-12794: - Committed to master. Unsure if I need to cherry-pick this somewhere else. It's docs so I guess not? > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Attachment: HBASE-12794-v1.patch Attached what I'll commit (with the question marks). Thanks all! > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Status: Patch Available (was: Open) > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Status: Open (was: Patch Available) > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch, HBASE-12794-v1.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Fix Version/s: 2.0.0 Affects Version/s: 2.0.0-alpha-1 Status: Patch Available (was: Open) > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Affects Versions: 2.0.0-alpha-1 >Reporter: stack >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-12794.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-12794: Attachment: HBASE-12794.patch Added info from the linked Google Doc and did some light reformatting of this area of the file. > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: stack >Assignee: Misty Stanley-Jones > Attachments: HBASE-12794.patch > > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-12794) Guidelines for filing JIRA issues
[ https://issues.apache.org/jira/browse/HBASE-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones reassigned HBASE-12794: --- Assignee: Misty Stanley-Jones (was: stack) > Guidelines for filing JIRA issues > - > > Key: HBASE-12794 > URL: https://issues.apache.org/jira/browse/HBASE-12794 > Project: HBase > Issue Type: Task > Components: documentation >Reporter: stack >Assignee: Misty Stanley-Jones > > Following on from Andrew's JIRA year-end cleaning spree, lets get some > guidelines on filing issues e.g. fill out all pertinent fields, add context > and provenance, add value (i.e. triage), don't file issues that are nought > but repeat of info available elsewhere (build box or mailing list), be > reluctant filing issues that don't have a resource behind them, don't file > issues on behalf of others, don't split fixes across multiple issues (because > there are poor folks coming behind us trying to backport our mess and > piecemeal makes their jobs harder), and so on. > The guidelines are not meant to put a chill on the opening of issues when > problems are found, especially not for new contributors. They are more meant > for quoting to veteran contributors who continue to file issues in violation > of what was thought a common understanding; rather than explain each time why > an issue has been marked invalid, it would be better if we can quote chapter > and verse from the refguide. > Dump any suggestion in here and I'll wind them up as a patch that I'll run by > dev mailing list to get consensus before committing. > Here is a running google doc if you'd like to add comment: > https://docs.google.com/document/d/1p3ArVLcnQnifk6ZsF635qWBhMmfTUJsISyK15DXnam0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-16750) hbase compilation failed
[
https://issues.apache.org/jira/browse/HBASE-16750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543373#comment-15543373
]
Misty Stanley-Jones commented on HBASE-16750:
-
+1 if the site builds and you have spot-checked it. I can't test it from here.
> hbase compilation failed
>
>
> Key: HBASE-16750
> URL: https://issues.apache.org/jira/browse/HBASE-16750
> Project: HBase
> Issue Type: Bug
> Components: build, documentation
>Affects Versions: 1.1.2
>Reporter: Saravanan Krishnamoorthy
>Assignee: Saravanan Krishnamoorthy
> Fix For: 1.1.2
>
> Attachments: HBASE-16750.branch-1.1.patch
>
>
> Hi,
> hbase compilation failed on IBM power system ppc64le architecture with below
> error:
> {code}
> Hbase Failure:
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:33 min
> [INFO] Finished at: 2016-09-30T08:58:47-04:00
> [INFO] Final Memory: 215M/843M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc
> (output-pdf) on project hbase: Execution output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> output-pdf of goal
> org.asciidoctor:asciidoctor-maven-plugin:1.5.2.1:process-asciidoc failed:
> (NotImplementedError) fstat unimplemented unsupported or native support
> failed to load
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: org.jruby.exceptions.RaiseException: (NotImplementedError) fstat
> unimplemented unsupported or native support failed to load
> at org.jruby.RubyFile.size(org/jruby/RubyFile.java:1108)
> at
> RUBY.render_body(/grid/0/jenkins/.m2/repository/org/asciidoctor/asciidoctorj-pdf/1.5.0-alpha.6/asciidoctorj-pdf-1.5.0-alpha.6.jar!/gems/pdf-core-0.2.5/lib/pdf/core/document_state.rb:69)
> at
>
[jira] [Commented] (HBASE-16544) Remove or Clarify 'Using Amazon S3 Storage' section in the reference guide
[ https://issues.apache.org/jira/browse/HBASE-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15459192#comment-15459192 ] Misty Stanley-Jones commented on HBASE-16544: - My mistake, due to not understanding S3 properly at the time. Feel free to remove. > Remove or Clarify 'Using Amazon S3 Storage' section in the reference guide > --- > > Key: HBASE-16544 > URL: https://issues.apache.org/jira/browse/HBASE-16544 > Project: HBase > Issue Type: Bug > Components: documentation, Filesystem Integration >Affects Versions: 2.0.0 >Reporter: Yi Liang >Assignee: Yi Liang > > reference guide at https://hbase.apache.org/book.html#amazon_s3_configuration > (1) the title 'Using Amazon S3 Storage' is confusing.From my point of view, I > think this title means that we can use S3 storage to replace HDFS, I really > tried this :(, always give me errors and hbase even can not start, see > error mentioned in jira HBASE-11045. > (2) And the details in this section are more about deploying HBase on Amazon > EC2 cluster, which has nothing to do 'using Amazon S3 storage' > (3) In all, I think we need to remove this section, or at least clarify this > section if someone fully test HBase on S3. see HBASE-15646 for more details > about this doc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16426) Remove company affiliations from committer list
[ https://issues.apache.org/jira/browse/HBASE-16426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16426: Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Pushed to master. Will be live when the site is next pushed. > Remove company affiliations from committer list > --- > > Key: HBASE-16426 > URL: https://issues.apache.org/jira/browse/HBASE-16426 > Project: HBase > Issue Type: Task > Components: documentation, website >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16426.patch > > > An email thread on the dev mailing list came to the consensus that company > affiliations in the committer list are difficult to keep up to date and not > worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16426) Remove company affiliations from committer list
[ https://issues.apache.org/jira/browse/HBASE-16426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16426: Component/s: website > Remove company affiliations from committer list > --- > > Key: HBASE-16426 > URL: https://issues.apache.org/jira/browse/HBASE-16426 > Project: HBase > Issue Type: Task > Components: documentation, website >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Attachments: HBASE-16426.patch > > > An email thread on the dev mailing list came to the consensus that company > affiliations in the committer list are difficult to keep up to date and not > worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16426) Remove company affiliations from committer list
[ https://issues.apache.org/jira/browse/HBASE-16426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16426: Status: Patch Available (was: Open) > Remove company affiliations from committer list > --- > > Key: HBASE-16426 > URL: https://issues.apache.org/jira/browse/HBASE-16426 > Project: HBase > Issue Type: Task > Components: documentation, website >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Attachments: HBASE-16426.patch > > > An email thread on the dev mailing list came to the consensus that company > affiliations in the committer list are difficult to keep up to date and not > worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16426) Remove company affiliations from committer list
[ https://issues.apache.org/jira/browse/HBASE-16426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16426: Component/s: documentation > Remove company affiliations from committer list > --- > > Key: HBASE-16426 > URL: https://issues.apache.org/jira/browse/HBASE-16426 > Project: HBase > Issue Type: Task > Components: documentation, website >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Attachments: HBASE-16426.patch > > > An email thread on the dev mailing list came to the consensus that company > affiliations in the committer list are difficult to keep up to date and not > worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16426) Remove company affiliations from committer list
[ https://issues.apache.org/jira/browse/HBASE-16426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16426: Attachment: HBASE-16426.patch Ready for review. [~apurtell] [~stack] [~busbey] > Remove company affiliations from committer list > --- > > Key: HBASE-16426 > URL: https://issues.apache.org/jira/browse/HBASE-16426 > Project: HBase > Issue Type: Task >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Attachments: HBASE-16426.patch > > > An email thread on the dev mailing list came to the consensus that company > affiliations in the committer list are difficult to keep up to date and not > worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16426) Remove company affiliations from committer list
Misty Stanley-Jones created HBASE-16426: --- Summary: Remove company affiliations from committer list Key: HBASE-16426 URL: https://issues.apache.org/jira/browse/HBASE-16426 Project: HBase Issue Type: Task Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones An email thread on the dev mailing list came to the consensus that company affiliations in the committer list are difficult to keep up to date and not worth it. This JIRA is to track removing them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16347) Unevaluated expressions in book
[
https://issues.apache.org/jira/browse/HBASE-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-16347:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Unevaluated expressions in book
> ---
>
> Key: HBASE-16347
> URL: https://issues.apache.org/jira/browse/HBASE-16347
> Project: HBase
> Issue Type: Bug
> Components: documentation, site
>Reporter: Nick Dimiduk
>Assignee: Dima Spivak
> Fix For: 2.0.0
>
> Attachments: HBASE-16347.patch, after-patch.png
>
>
> Have a look at the [quickstart
> guide|http://hbase.apache.org/book.html#quickstart], step two
> {noformat}
> $ tar xzvf hbase--bin.tar.gz
> $ cd hbase-/
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16347) Unevaluated expressions in book
[
https://issues.apache.org/jira/browse/HBASE-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-16347:
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
> Unevaluated expressions in book
> ---
>
> Key: HBASE-16347
> URL: https://issues.apache.org/jira/browse/HBASE-16347
> Project: HBase
> Issue Type: Bug
> Components: documentation, site
>Reporter: Nick Dimiduk
>Assignee: Dima Spivak
> Fix For: 2.0.0
>
> Attachments: HBASE-16347.patch, after-patch.png
>
>
> Have a look at the [quickstart
> guide|http://hbase.apache.org/book.html#quickstart], step two
> {noformat}
> $ tar xzvf hbase--bin.tar.gz
> $ cd hbase-/
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-16347) Unevaluated expressions in book
[
https://issues.apache.org/jira/browse/HBASE-16347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406655#comment-15406655
]
Misty Stanley-Jones commented on HBASE-16347:
-
+1, committed to master. Thanks [~dspivak]!
> Unevaluated expressions in book
> ---
>
> Key: HBASE-16347
> URL: https://issues.apache.org/jira/browse/HBASE-16347
> Project: HBase
> Issue Type: Bug
> Components: documentation, site
>Reporter: Nick Dimiduk
>Assignee: Dima Spivak
> Fix For: 2.0.0
>
> Attachments: HBASE-16347.patch, after-patch.png
>
>
> Have a look at the [quickstart
> guide|http://hbase.apache.org/book.html#quickstart], step two
> {noformat}
> $ tar xzvf hbase--bin.tar.gz
> $ cd hbase-/
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16279) Separate and rewrite intro and quickstart
[ https://issues.apache.org/jira/browse/HBASE-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16279: Attachment: HBASE-16279-v1.patch This patch addresses [~daniel_vimont]'s feedback and adds back the important installation notes / prereqs as an appendix. It also renames the new directory from intro/ to installation/. > Separate and rewrite intro and quickstart > - > > Key: HBASE-16279 > URL: https://issues.apache.org/jira/browse/HBASE-16279 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16279-v1.patch, HBASE-16279.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16279) Separate and rewrite intro and quickstart
[ https://issues.apache.org/jira/browse/HBASE-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16279: Status: Open (was: Patch Available) > Separate and rewrite intro and quickstart > - > > Key: HBASE-16279 > URL: https://issues.apache.org/jira/browse/HBASE-16279 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16279-v1.patch, HBASE-16279.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16279) Separate and rewrite intro and quickstart
[ https://issues.apache.org/jira/browse/HBASE-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16279: Status: Patch Available (was: Open) > Separate and rewrite intro and quickstart > - > > Key: HBASE-16279 > URL: https://issues.apache.org/jira/browse/HBASE-16279 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16279-v1.patch, HBASE-16279.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16279) Separate and rewrite intro and quickstart
[ https://issues.apache.org/jira/browse/HBASE-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16279: Status: Patch Available (was: Open) > Separate and rewrite intro and quickstart > - > > Key: HBASE-16279 > URL: https://issues.apache.org/jira/browse/HBASE-16279 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16279.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16279) Separate and rewrite intro and quickstart
[ https://issues.apache.org/jira/browse/HBASE-16279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16279: Attachment: HBASE-16279.patch cc [~stack] [~busbey] > Separate and rewrite intro and quickstart > - > > Key: HBASE-16279 > URL: https://issues.apache.org/jira/browse/HBASE-16279 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: Misty Stanley-Jones >Assignee: Misty Stanley-Jones > Fix For: 2.0.0 > > Attachments: HBASE-16279.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-16279) Separate and rewrite intro and quickstart
Misty Stanley-Jones created HBASE-16279: --- Summary: Separate and rewrite intro and quickstart Key: HBASE-16279 URL: https://issues.apache.org/jira/browse/HBASE-16279 Project: HBase Issue Type: Sub-task Components: documentation Reporter: Misty Stanley-Jones Assignee: Misty Stanley-Jones -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-15305) Fix a couple of incorrect anchors in HBase ref guide
[
https://issues.apache.org/jira/browse/HBASE-15305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-15305:
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks!
> Fix a couple of incorrect anchors in HBase ref guide
>
>
> Key: HBASE-15305
> URL: https://issues.apache.org/jira/browse/HBASE-15305
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-15305-v2.patch
>
>
> From HBASE-15298:
> {quote}
> After this patch is applied, there are still two missing asciidoc anchors,
> distributed.log.splitting and fail.fast.expired.active.master. These are
> related to features removed by HBASE-14053 and HBASE-10569. I think these
> anchors(and related texts) should be handled by someone who knows those
> issues well, so I retain them.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-16183) Correct errors in example programs of coprocessor in Ref Guide
[ https://issues.apache.org/jira/browse/HBASE-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16183: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thank you! Pushed. > Correct errors in example programs of coprocessor in Ref Guide > -- > > Key: HBASE-16183 > URL: https://issues.apache.org/jira/browse/HBASE-16183 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.2.0 >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > Labels: documentaion > Fix For: 2.0.0 > > Attachments: HBASE-16183-master-v1.patch, > HBASE-16183.master.002.patch, HBASE-16183.patch > > > There are some errors in the example programs for coprocessor in Ref Guide. > Such as using deprecated APIs, generic... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14813) REST documentation under package.html should go to the book
[
https://issues.apache.org/jira/browse/HBASE-14813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-14813:
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thank you!
> REST documentation under package.html should go to the book
> ---
>
> Key: HBASE-14813
> URL: https://issues.apache.org/jira/browse/HBASE-14813
> Project: HBase
> Issue Type: Improvement
> Components: documentation, REST
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
> Attachments: HBASE-14813-v1.patch, HBASE-14813.patch
>
>
> It seems that we have more up to date and better documentation under
> {{hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/package.html}} than
> in the book. We should merge these two. The package.html is only accessible
> if you know where to look.
> [~misty] FYI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15305) Fix a couple of incorrect anchors in HBase ref guide
[
https://issues.apache.org/jira/browse/HBASE-15305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-15305:
Attachment: (was: HBASE-15305.patch)
> Fix a couple of incorrect anchors in HBase ref guide
>
>
> Key: HBASE-15305
> URL: https://issues.apache.org/jira/browse/HBASE-15305
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-15305-v2.patch
>
>
> From HBASE-15298:
> {quote}
> After this patch is applied, there are still two missing asciidoc anchors,
> distributed.log.splitting and fail.fast.expired.active.master. These are
> related to features removed by HBASE-14053 and HBASE-10569. I think these
> anchors(and related texts) should be handled by someone who knows those
> issues well, so I retain them.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15305) Fix a couple of incorrect anchors in HBase ref guide
[
https://issues.apache.org/jira/browse/HBASE-15305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-15305:
Attachment: (was: HBASE-15298-v1.patch)
> Fix a couple of incorrect anchors in HBase ref guide
>
>
> Key: HBASE-15305
> URL: https://issues.apache.org/jira/browse/HBASE-15305
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-15305-v2.patch
>
>
> From HBASE-15298:
> {quote}
> After this patch is applied, there are still two missing asciidoc anchors,
> distributed.log.splitting and fail.fast.expired.active.master. These are
> related to features removed by HBASE-14053 and HBASE-10569. I think these
> anchors(and related texts) should be handled by someone who knows those
> issues well, so I retain them.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15305) Fix a couple of incorrect anchors in HBase ref guide
[
https://issues.apache.org/jira/browse/HBASE-15305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-15305:
Attachment: HBASE-15305-v2.patch
Please disregard the patches older than today.
> Fix a couple of incorrect anchors in HBase ref guide
>
>
> Key: HBASE-15305
> URL: https://issues.apache.org/jira/browse/HBASE-15305
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
>Reporter: Misty Stanley-Jones
>Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-15305-v2.patch
>
>
> From HBASE-15298:
> {quote}
> After this patch is applied, there are still two missing asciidoc anchors,
> distributed.log.splitting and fail.fast.expired.active.master. These are
> related to features removed by HBASE-14053 and HBASE-10569. I think these
> anchors(and related texts) should be handled by someone who knows those
> issues well, so I retain them.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14813) REST documentation under package.html should go to the book
[
https://issues.apache.org/jira/browse/HBASE-14813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Misty Stanley-Jones updated HBASE-14813:
Attachment: HBASE-14813-v1.patch
Rebased on something recent, and added the protobuf accept header.
> REST documentation under package.html should go to the book
> ---
>
> Key: HBASE-14813
> URL: https://issues.apache.org/jira/browse/HBASE-14813
> Project: HBase
> Issue Type: Improvement
> Components: documentation, REST
>Reporter: Enis Soztutar
>Assignee: Misty Stanley-Jones
> Attachments: HBASE-14813-v1.patch, HBASE-14813.patch
>
>
> It seems that we have more up to date and better documentation under
> {{hbase-rest/src/main/java/org/apache/hadoop/hbase/rest/package.html}} than
> in the book. We should merge these two. The package.html is only accessible
> if you know where to look.
> [~misty] FYI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-15473) Documentation for the usage of hbase dataframe user api (JSON, Avro, etc)
[ https://issues.apache.org/jira/browse/HBASE-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-15473: Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) LGTM, committed to master. Thanks for this large revision, [~Weiqing Yang] > Documentation for the usage of hbase dataframe user api (JSON, Avro, etc) > - > > Key: HBASE-15473 > URL: https://issues.apache.org/jira/browse/HBASE-15473 > Project: HBase > Issue Type: Sub-task > Components: documentation, spark >Reporter: Zhan Zhang >Assignee: Weiqing Yang >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-15473_v1.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-16183) Correct errors in example program of coprocessor in Ref Guide
[ https://issues.apache.org/jira/browse/HBASE-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-16183: Status: Open (was: Patch Available) Please re-create and re-attach the patch. > Correct errors in example program of coprocessor in Ref Guide > - > > Key: HBASE-16183 > URL: https://issues.apache.org/jira/browse/HBASE-16183 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 1.2.0 >Reporter: Xiang Li >Assignee: Xiang Li >Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-16183-master-v1.patch, HBASE-16183.patch > > > There are some errors in the example programs for coprocessor in Ref Guide. > Such as using deprecated APIs, generic... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
