Skip to content

[ZEPPELIN-6440] Refresh stale virtual machine and YARN deployment documentation - #5580

Open
soheetech wants to merge 1 commit into
apache:masterfrom
soheetech:ZEPPELIN-6440
Open

soheetech wants to merge 1 commit into
apache:masterfrom
soheetech:ZEPPELIN-6440

Conversation

@soheetech

Copy link
Copy Markdown
Contributor

What is this PR for?

This PR refreshes legacy deployment documentation (virtual_machine.md and yarn_install.md) to resolve outdated prerequisites and deprecated repository URLs.
It explicitly frames legacy VM provisioning and Hortonworks HDP 2.3.1 setups (CentOS 6, Java 7/8, Spark 1.6, Hadoop 2.7) as historical references rather than current contributor guides, and points readers to active build guides and official GitHub repository URLs.

What type of PR is it?

Documentation

Todos

  • - Mark legacy VM provisioning and the HDP 2.3.1 YARN setup as historical references
  • - Clarify that the documented Java 8 and Spark 1.6 examples are not current development requirements
  • - Replace the clone example with the official GitHub HTTPS URL

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-6440

How should this be tested?

  1. Verify stale references are removed or properly contextualized as historical examples via search:
   git grep -n -E "git://git.apache.org|openjdk-7-jdk|0\.12\.7|Spark 1\.6|Hadoop 2\.4" -- docs/setup/deployment/virtual_machine.md docs/setup/deployment/yarn_install.md README.md
  • Confirmed git://git.apache.org is completely removed.
  • Confirmed remaining Spark 1.6 references in yarn_install.md are clearly framed as historical examples.
  1. Run whitespace and format validation:
git diff --check

Questions:

  • Does the license files need to update? No
  • Is there breaking changes for older versions? No
  • Does this needs documentation? No (this PR updates documentation itself)

…umentation

- Mark legacy VM provisioning and YARN cluster setups as historical references
- Clarify that Java 7/8, Node 0.12, and Spark 1.6 are not current development requirements
- Replace obsolete git clone URLs with official GitHub repository URLs

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant