Skip to content

[SPARK-20400][DOCS] Remove References to 3rd Party Vendor Tools #17695

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
bllchmbrs wants to merge 2 commits into from
Closed

[SPARK-20400][DOCS] Remove References to 3rd Party Vendor Tools #17695

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5692124
remove references to vendors
Apr 20, 2017
e74c2d6
fix
Apr 23, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2248,8 +2248,8 @@ should be included on Spark's classpath:
* `hdfs-site.xml`, which provides default behaviors for the HDFS client.
* `core-site.xml`, which sets the default filesystem name.

The location of these configuration files varies across CDH and HDP versions, but
a common location is inside of `/etc/hadoop/conf`. Some tools, such as Cloudera Manager, create
The location of these configuration files varies across hadoop versions, but

@srowen srowen Apr 20, 2017

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hadoop -> Hadoop

@srowen srowen Apr 22, 2017

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping @anabranch

a common location is inside of `/etc/hadoop/conf`. Some tools create

@srowen srowen Apr 20, 2017

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This also won't matter either way, but is an example of an instance where naming a specific product is helpful information for users. There's no policy against this. But, it can be removed, sure, it's trivial either way.

configurations on-the-fly, but offer a mechanisms to download copies of them.

To make these files visible to Spark, set `HADOOP_CONF_DIR` in `$SPARK_HOME/spark-env.sh`
Expand Down