This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hive-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new b4b499a deploy: 4190918d3489c61fa8769007bcf8f2ea26bfceaf
b4b499a is described below
commit b4b499acf4b8823d8fb4ed3770dc009298c8363f
Author: zhangbutao <[email protected]>
AuthorDate: Wed Aug 13 01:29:51 2025 +0000
deploy: 4190918d3489c61fa8769007bcf8f2ea26bfceaf
---
.../resources/howtorelease_27362106/index.html | 104 +++++++++++++--------
index.json | 2 +-
2 files changed, 68 insertions(+), 38 deletions(-)
diff --git a/community/resources/howtorelease_27362106/index.html
b/community/resources/howtorelease_27362106/index.html
index 6c26f97..03285cc 100644
--- a/community/resources/howtorelease_27362106/index.html
+++ b/community/resources/howtorelease_27362106/index.html
@@ -326,17 +326,22 @@ git checkout branch-X.Y
<li>Update the <code>version</code> property value in all pom.xml files. You
should remove the <code>SNAPSHOT</code> suffix and set <code>version</code>
equal to <code>hive-X.Y.Z</code> where Z is the point release number in this
release series (0 for the first one, in which case this step is a no-op since
you already did this above when creating the branch). Use <a
href=http://mojo.codehaus.org/versions-maven-plugin/set-mojo.html>Maven’s
Versions plugin</a> to do this as follows:</li>
</ol>
<pre tabindex=0><code>mvn versions:set -DnewVersion=0.7.0
-DgenerateBackupPoms=false
-</code></pre><p>Make sure to update the version property in
standalone-metastore/pom.xml and upgrade-acid/pom.xml.
-3. Remove the storage-api from the list of modules to build in the top level
pom.xml. Set the storage-api.version property to the release of storage-api
that you are using for your release. Make sure to set the storage-api.version
property in standalone-metastore/pom.xml as well.
-4. Update the the value of the <code>TRACKING_BRANCH</code> field in the
<code>.reviewboardrc</code> file to point to the <code>origin/branch-X.Y</code>.
-5. Verify that the build is working with changes.
-6. Commit these changes with a comment “Preparing for X.Y.Z
release”.
-7. If not already done, merge desired patches from trunk into the branch and
commit these changes. Avoid usage of “git merge” to avoid too many
merge commits. Either request the committer who committed that patch in master
to commit to this branch, or commit it yourself, or try doing a git cherry-pick
for trivial patches. Specifics of this step can be laid down by the release
manager.
-8. You probably also want to commit a patch (on both trunk and branch) which
updates README.txt to bring it up to date (at a minimum, search+replacing
references to the version number). Also check NOTICE to see if anything needs
to be updated for recent library dependency changes or additions.
-1. Select all of the JIRAs for the current release that aren’t FIXED and
do bulk update to clear the ‘Fixed Version’ field.
-2. Likewise, use JIRA’s <a
href="https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310843";>Release
Notes</a> link to generate content for the RELEASE_NOTES.txt file. Be sure to
select ‘Text’ format. (It’s OK to do this with a direct
commit rather than a patch.)
-3. Update the release notes in trunk with the release notes in branch.
-9. Tag the release candidate (R is the release candidate number, and also
starts from 0):</p>
+</code></pre><p>Make sure to update the version property in
standalone-metastore/pom.xml and upgrade-acid/pom.xml.</p>
+<ol start=3>
+<li>Remove the storage-api from the list of modules to build in the top level
pom.xml. Set the storage-api.version property to the release of storage-api
that you are using for your release. Make sure to set the storage-api.version
property in standalone-metastore/pom.xml as well.</li>
+<li>Update the the value of the <code>TRACKING_BRANCH</code> field in the
<code>.reviewboardrc</code> file to point to the
<code>origin/branch-X.Y</code>.</li>
+<li>Verify that the build is working with changes.</li>
+<li>Commit these changes with a comment “Preparing for X.Y.Z
release”.</li>
+<li>If not already done, merge desired patches from trunk into the branch and
commit these changes. Avoid usage of “git merge” to avoid too many
merge commits. Either request the committer who committed that patch in master
to commit to this branch, or commit it yourself, or try doing a git cherry-pick
for trivial patches. Specifics of this step can be laid down by the release
manager.</li>
+<li>You probably also want to commit a patch (on both trunk and branch) which
updates README.txt to bring it up to date (at a minimum, search+replacing
references to the version number). Also check NOTICE to see if anything needs
to be updated for recent library dependency changes or additions.
+<ol>
+<li>Select all of the JIRAs for the current release that aren’t FIXED
and do bulk update to clear the ‘Fixed Version’ field.</li>
+<li>Likewise, use JIRA’s <a
href="https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310843";>Release
Notes</a> link to generate content for the RELEASE_NOTES.txt file. Be sure to
select ‘Text’ format. (It’s OK to do this with a direct
commit rather than a patch.)</li>
+<li>Update the release notes in trunk with the release notes in branch.</li>
+</ol>
+</li>
+<li>Tag the release candidate (R is the release candidate number, and also
starts from 0):</li>
+</ol>
<pre tabindex=0><code>git tag -a release-X.Y.Z-rcR -m "Hive X.Y.Z-rcR
release."
git push origin release-X.Y.Z-rcR
</code></pre><h3 id=building>Building</h3>
@@ -353,8 +358,10 @@ git push origin release-X.Y.Z-rcR
% cd ../../standalone-metastore/packaging/target
% shasum -a 256 hive-standalone-metastore-X.Y.Z-bin.tar.gz >
hive-standalone-metastore-X.Y.Z-bin.tar.gz.sha256
% shasum -a 256 hive-standalone-metastore-X.Y.Z-src.tar.gz >
hive-standalone-metastore-X.Y.Z-src.tar.gz.sha256
-</code></pre><p>Note: If you build from the existing project, make sure there
are no empty directories or the “*.iml” files in the
apache-hive-X.Y.Z-src.tar.gz.
-3. Verify that the SHA 256 checksums are valid:</p>
+</code></pre><p>Note: If you build from the existing project, make sure there
are no empty directories or the “*.iml” files in the
apache-hive-X.Y.Z-src.tar.gz.</p>
+<ol start=3>
+<li>Verify that the SHA 256 checksums are valid:</li>
+</ol>
<pre tabindex=0><code>% shasum -a 256 -c apache-hive-X.Y.Z-bin.tar.gz.sha256
apache-hive-X.Y.Z-bin.tar.gz: OK
@@ -389,7 +396,7 @@ hive-standalone-metastore-X.Y.Z-src.tar.gz: OK
% gpg --armor --output hive-standalone-metastore-X.Y.Z-bin.tar.gz.asc
--detach-sig hive-standalone-metastore-X.Y.Z-bin.tar.gz
% gpg --armor --output hive-standalone-metastore-X.Y.Z-src.tar.gz.asc
--detach-sig hive-standalone-metastore-X.Y.Z-src.tar.gz
</code></pre><ol start=7>
-<li>Follow instructions in <a
href=https://www.apache.org/dev/release-publishing.html#distribution>https://www.apache.org/dev/release-publishing.html#distribution</a>
to push the new release artifacts (tar.gz, tar.gz.asc, tar.gz.sha256) to the
SVN staging area of the project (<a
href=https://dist.apache.org/repos/dist/dev/hive/>https://dist.apache.org/repos/dist/dev/hive/</a>).
Make sure to create a new directory for the release candidate. You may need
PMC privileges to do this step – if [...]
+<li>Follow instructions in <a
href=https://www.apache.org/dev/release-publishing.html#distribution>https://www.apache.org/dev/release-publishing.html#distribution</a>
to push the new release artifacts (tar.gz, tar.gz.asc, tar.gz.sha256) to the
SVN staging area of the project (<a
href=https://dist.apache.org/repos/dist/dev/hive/>https://dist.apache.org/repos/dist/dev/hive/</a>).
Make sure to create a new directory for the release candidate.</li>
</ol>
<pre tabindex=0><code>svn co --depth empty https://dist.apache.org/repos/dist
cd dist
@@ -422,7 +429,8 @@ Subject: [VOTE] Apache Hive X.Y.Z Release Candidate N
Apache Hive X.Y.Z Release Candidate N is available here:
-https://people.apache.org/~you/hive-X.Y.Z-candidate-N
+https://dist.apache.org/repos/dist/dev/hive/hive-X.Y.Z/
+https://dist.apache.org/repos/dist/dev/hive/hive-standalone-metastore-X.Y.Z/
The checksums are these:
- ff60286044d2f3faa8ad1475132cdcecf4ce9ed8faf1ed4e56a6753ebc3ab585
apache-hive-4.1.0-bin.tar.gz
@@ -441,9 +449,17 @@ The git commit hash is:
https://github.com/apache/hive/commit/357d4906f5c806d585fd84db57cf296e12e6049b
-Voting will conclude in 72 hours.
+The vote is open for the next 72 hours and passes if a majority of at least
+three +1 PMC votes are cast.
+
+(Only PMC members have binding votes, however, other community members
+are encouraged to cast non-binding votes.)
+
+[ ] +1 Release this package as Apache Hive X.Y.Z
+[ ] +0
+[ ] -1 Do not release this because...
-Hive PMC Members: Please test and vote.
+Please download, verify, and test.
Thanks.
</code></pre><p>After the vote finishes, count <em>all</em> votes and send out
the result in a separate thread.</p>
@@ -508,31 +524,40 @@ See the step under Building.</li>
<ol>
<li>Tag the release and delete the release candidate tag. Do it from the
release branch:</li>
</ol>
-<pre tabindex=0><code>git tag -s rel/release-X.Y.Z -m "HiveX.Y.Z
release."
+<pre tabindex=0><code>git tag -s rel/release-X.Y.Z -m "Hive X.Y.Z
release."
git push origin rel/release-X.Y.Z
git tag -d release-X.Y.Z-rcR
git push origin :release-X.Y.Z-rcR
-</code></pre><p>If errors happen while “git tag -s”, try to
configure the git signing key by “git config user.signingkey
your_gpg_key_id” then rerun the command.
-2. Move the release artifacts to the release area of the project (<a
href=https://dist.apache.org/repos/dist/release/hive/>https://dist.apache.org/repos/dist/release/hive/</a>).
Using svn mv command is important otherwise you may hit size limitations
applying to artifacts(<a
href=https://issues.apache.org/jira/browse/INFRA-23055>INFRA-23055</a>)</p>
+</code></pre><p><strong>NOTE:</strong><br>
+If errors happen while “git tag -s”, try to configure the git
signing key by “git config user.signingkey your_gpg_key_id” then
rerun the command.<br>
+This step (<code>git push origin rel/release-X.Y.Z</code>) will trigger the
Hive Docker image build and upload to Docker Hub on the <a
href=https://github.com/apache/hive/actions/workflows/docker-GA-images.yml>Hive
Action Page</a>. If the image build fails, click <strong>Re-run</strong> on the
Actions page to retry or manually build and upload it. Finally, verify whether
the image has been successfully uploaded by checking the <a
href=https://hub.docker.com/r/apache/hive/tags>Docker Hub< [...]
+<ol start=2>
+<li>Move the release artifacts to the release area of the project (<a
href=https://dist.apache.org/repos/dist/release/hive/>https://dist.apache.org/repos/dist/release/hive/</a>).
Using svn mv command is important otherwise you may hit size limitations
applying to artifacts(<a
href=https://issues.apache.org/jira/browse/INFRA-23055>INFRA-23055</a>).</li>
+</ol>
<pre tabindex=0><code>svn mv
https://dist.apache.org/repos/dist/dev/hive/hive-X.Y.Z
https://dist.apache.org/repos/dist/release/hive/hive-X.Y.Z -m "Move
hive-X.Y.Z release from dev to release"
+svn mv
https://dist.apache.org/repos/dist/dev/hive/hive-standalone-metastore-X.Y.Z
https://dist.apache.org/repos/dist/release/hive/hive-standalone-metastore-X.Y.Z
-m "Move hive-standalone-metastore-X.Y.Z release from dev to release"
</code></pre><ol start=3>
<li>Wait till the release propagates to the mirrors and appears under: <a
href=https://dlcdn.apache.org/hive/>https://dlcdn.apache.org/hive/</a></li>
<li>In your base hive source directory, generate javadocs as follows:</li>
</ol>
<pre tabindex=0><code>mvn clean install javadoc:javadoc javadoc:aggregate
-Pjavadoc -DskipTests
-</code></pre><p>After you run this, you should have javadocs present in your
<hive_source_dir>/target/site/apidocs
-5. Check out the javadocs svn repository as follows:</p>
+</code></pre><p>After you run this, you should have javadocs present in your
<hive_source_dir>/target/site/apidocs.</p>
+<ol start=5>
+<li>Check out the javadocs svn repository as follows:</li>
+</ol>
<pre tabindex=0><code>svn co --depth empty
https://svn.apache.org/repos/infra/websites/production/hive/content/javadocs
</code></pre><ol start=6>
<li>Copy the generated javadocs from the source repository to the javadocs
repository, add and commit:</li>
</ol>
-<pre tabindex=0><code>mkdir <hive_javadocs_repo_dir>/rX.Y.Z/
-cd <hive_javadocs_repo_dir>
+<pre tabindex=0><code>mkdir ./javadocs/rX.Y.Z/
+cd javadocs
cp -r <hive_source_dir>/target/site/apidocs ./rX.Y.Z/api
svn add rX.Y.Z
-svn commit
-</code></pre><p>If this is a bugfix release, svn rm the obsoleted version.
(For eg., when committing javadocs for r0.13.1, r0.13.0 would have been removed)
-7. Prepare to edit the website.</p>
+svn commit -m "Hive X.Y.Z javadocs"
+</code></pre><p>If this is a bugfix release, svn rm the obsoleted version.
(For eg., when committing javadocs for r0.13.1, r0.13.0 would have been
removed)</p>
+<ol start=7>
+<li>Prepare to edit the website.</li>
+</ol>
<pre tabindex=0><code>git clone https://github.com/apache/hive-site.git
</code></pre><ol start=8>
<li>Edit files content/downloads.mdtext and javadoc.mdtext to appropriately
add entries for the new release in the appropriate location. For example, for
1.2.0, the entries made were as follows:</li>
@@ -542,16 +567,21 @@ svn commit
./downloads.md:[HIVE_1_2_0_CL]:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&styleName=Text&projectId=12310843
./javadoc.md: * [Hive 1.2.0 Javadocs][r1.2.0]
./javadoc.md:[r1.2.0]: /javadocs/r1.2.0/api/index.html
-</code></pre><p>As you can see, you will need a release note link for this
release as created previously for this section.
-9. Push your changes to the <a
href=https://github.com/apache/hive-site/tree/gh-pages>https://github.com/apache/hive-site/tree/gh-pages</a>
branch, and you can preview the results at <a
href=https://apache.github.io/hive-site/>https://apache.github.io/hive-site/</a>.
If everything is ok, then you can push your changes to <a
href=https://github.com/apache/hive-site/tree/main>https://github.com/apache/hive-site/tree/main</a>
branch and see the results at <a href=https://hive.apache.org/>ht [...]
-10. Update JIRA
-1. Ensure that only issues in the “Fixed” state have a “Fix
Version” set to release X.Y.Z.
-2. Release the version. Visit the <a
href="https://issues.apache.org/jira/projects/HIVE?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased";>releases
page</a>. Select the version number you are releasing, and hit the release
button. You need to have the “Admin” role in Hive’s Jira for
this step and the next.
-3. Close issues resolved in the release. Disable mail notifications for this
bulk change.
-11. Login to the <a
href=https://repository.apache.org/index.html#stagingRepositories>Apache Nexus
server</a> and mark the release candidate artifacts as released.
-12. Add the release in <a
href=https://reporter.apache.org/addrelease.html?hive>Apache Committee Report
Helper</a> for the next board report to pick that up automatically.
-13. Check whether the <a href=https://hub.docker.com/r/apache/hive>Docker
image</a> for the release is present or not.
-14. Send a release announcement to Hive <code>user</code> and <code>dev</code>
lists as well as the Apache <code>announce</code> list. This email should be
sent from your Apache email address:</p>
+</code></pre><p>As you can see, you will need a release note link for this
release as created previously for this section.</p>
+<ol start=9>
+<li>Push your changes to the <a
href=https://github.com/apache/hive-site/tree/gh-pages>https://github.com/apache/hive-site/tree/gh-pages</a>
branch, and you can preview the results at <a
href=https://apache.github.io/hive-site/>https://apache.github.io/hive-site/</a>.
If everything is ok, then you can push your changes to <a
href=https://github.com/apache/hive-site/tree/main>https://github.com/apache/hive-site/tree/main</a>
branch and see the results at <a href=https://hive.apache.org/>h [...]
+<li>Update JIRA
+<ol>
+<li>Ensure that only issues in the “Fixed” state have a “Fix
Version” set to release X.Y.Z.</li>
+<li>Release the version. Visit the <a
href="https://issues.apache.org/jira/projects/HIVE?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased";>releases
page</a>. Select the version number you are releasing, and hit the release
button. You need to have the “Admin” role in Hive’s Jira for
this step and the next.</li>
+<li>Close issues resolved in the release. Disable mail notifications for this
bulk change.</li>
+</ol>
+</li>
+<li>Login to the <a
href=https://repository.apache.org/index.html#stagingRepositories>Apache Nexus
server</a> and mark the release candidate artifacts as released.</li>
+<li>Add the release in <a
href=https://reporter.apache.org/addrelease.html?hive>Apache Committee Report
Helper</a> for the next board report to pick that up automatically. You may
need PMC privileges to do this step – if you do not have such privileges,
please ping a <a href=http://hive.apache.org/people.html>PMC member</a> to do
this for you.</li>
+<li>Check whether the <a href=https://hub.docker.com/r/apache/hive>Docker
image</a> for the release is present or not.</li>
+<li>Send a release announcement to Hive <code>user</code> and <code>dev</code>
lists as well as the Apache <code>announce</code> list. This email should be
sent from your Apache email address:</li>
+</ol>
<pre tabindex=0><code>From: [email protected]
To: [email protected], [email protected], [email protected]
Subject: [ANNOUNCE] Apache Hive X.Y.Z Released
diff --git a/index.json b/index.json
index 495c3d3..692bc41 100644
--- a/index.json
+++ b/index.json
@@ -1 +1 @@
-[{"categories":null,"contents":"Background In Hive, lineage information is
captured in the form of LineageInfo object. This object is created in the
SemanticAnalyzer and is passed to the HookContext object. Users can use the
following existing Hooks or implement their own custom hooks to capture this
information and utilize it.\nExisting Hooks
org.apache.hadoop.hive.ql.hooks.PostExecutePrinter
org.apache.hadoop.hive.ql.hooks.LineageLogger
org.apache.atlas.hive.hook.HiveHook To facilita [...]
\ No newline at end of file
+[{"categories":null,"contents":"Background In Hive, lineage information is
captured in the form of LineageInfo object. This object is created in the
SemanticAnalyzer and is passed to the HookContext object. Users can use the
following existing Hooks or implement their own custom hooks to capture this
information and utilize it.\nExisting Hooks
org.apache.hadoop.hive.ql.hooks.PostExecutePrinter
org.apache.hadoop.hive.ql.hooks.LineageLogger
org.apache.atlas.hive.hook.HiveHook To facilita [...]
\ No newline at end of file
