accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] mikewalch closed pull request #143: Updated script docs from changes in master
Date Thu, 10 Jan 2019 16:28:54 GMT
mikewalch closed pull request #143: Updated script docs from changes in master
URL: https://github.com/apache/accumulo-website/pull/143
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/_docs-2/administration/in-depth-install.md b/_docs-2/administration/in-depth-install.md
index 524edd31..72c7f7d2 100644
--- a/_docs-2/administration/in-depth-install.md
+++ b/_docs-2/administration/in-depth-install.md
@@ -115,8 +115,8 @@ and specify the following:
 Accumulo uses `HADOOP_HOME` and `ZOOKEEPER_HOME` to locate Hadoop and Zookeeper jars
 and add them the `CLASSPATH` variable. If you are running a vendor-specific release of Hadoop
 or Zookeeper, you may need to change how your `CLASSPATH` is built in [accumulo-env.sh].
If
-Accumulo has problems later on finding jars, run `accumulo classpath -d` to debug and print
-Accumulo's classpath.
+Accumulo has problems later on finding jars, run `accumulo classpath` to print Accumulo's
+classpath.
 
 You may want to change the default memory settings for Accumulo's TabletServer which are
 by set in the `JAVA_OPTS` settings for 'tservers' in [accumulo-env.sh]. Note the
@@ -312,10 +312,12 @@ consideration. There is no enforcement of these warnings via the API.
 
 ### Configuring the ClassLoader
 
-Accumulo builds its Java classpath in [accumulo-env.sh].  After an Accumulo application has
started, it will load classes from the locations
-specified in the deprecated [general.classpaths] property. Additionally, Accumulo will load
classes from the locations specified in the
-[general.dynamic.classpaths] property and will monitor and reload them if they change. The
reloading feature is useful during the development
-and testing of iterators as new or modified iterator classes can be deployed to Accumulo
without having to restart the database.
+Accumulo builds its Java classpath in [accumulo-env.sh]. This classpath can be viewed by
running `accumulo classpath`.
+
+After an Accumulo application has started, it will load classes from the locations specified
in the deprecated [general.classpaths] property.
+Additionally, Accumulo will load classes from the locations specified in the [general.dynamic.classpaths]
property and will monitor and reload
+them if they change. The reloading feature is useful during the development and testing of
iterators as new or modified iterator classes can be
+deployed to Accumulo without having to restart the database.
 
 Accumulo also has an alternate configuration for the classloader which will allow it to load
classes from remote locations. This mechanism
 uses Apache Commons VFS which enables locations such as http and hdfs to be used. This alternate
configuration also uses the
@@ -323,8 +325,6 @@ uses Apache Commons VFS which enables locations such as http and hdfs
to be used
 [general.vfs.classpaths] property instead of the [general.dynamic.classpaths] property. As
in the default configuration, this alternate
 configuration will also monitor the vfs locations for changes and reload if necessary.
 
-The Accumulo classpath can be viewed in human readable format by running `accumulo classpath
-d`.
-
 ##### ClassLoader Contexts
 
 With the addition of the VFS based classloader, we introduced the notion of classloader contexts.
A context is identified
diff --git a/_docs-2/getting-started/clients.md b/_docs-2/getting-started/clients.md
index bda0c661..c73ec89f 100644
--- a/_docs-2/getting-started/clients.md
+++ b/_docs-2/getting-started/clients.md
@@ -305,7 +305,6 @@ of the different ways to execute client code.
 * build and execute an uber jar
 * add `accumulo classpath` to your Java classpath
 * use the `accumulo` command
-* use the `accumulo-util hadoop-jar` command
 
 ### Build and execute an uber jar
 
@@ -321,11 +320,6 @@ to include all of Accumulo's dependencies on your classpath:
 
     java -classpath /path/to/my.jar:/path/to/dep.jar:$(accumulo classpath) com.my.Main arg1
arg2
 
-If you would like to review which jars are included, the `accumulo classpath` command can
-output a more human readable format using the `-d` option which enables debugging:
-
-    accumulo classpath -d
-
 ### Use the accumulo command
 
 Another option for running your code is to use the Accumulo script which can execute a
@@ -341,12 +335,6 @@ the accumulo command.
 
     export CLASSPATH=/path/to/my.jar:/path/to/dep.jar; accumulo com.foo.Client arg1 arg2
 
-### Use the 'accumulo-util hadoop-jar' command
-
-If you are writing map reduce job that accesses Accumulo, then you can use
-`accumulo-util hadoop-jar` to run those jobs. See the [MapReduce example][mapred-example]
-for more information.
-
 ## Additional Documentation
 
 This page covers Accumulo client basics.  Below are links to additional documentation that
may be useful when creating Accumulo clients:
diff --git a/_docs-2/getting-started/quickstart.md b/_docs-2/getting-started/quickstart.md
index d5bb6bc5..5f2fa15b 100644
--- a/_docs-2/getting-started/quickstart.md
+++ b/_docs-2/getting-started/quickstart.md
@@ -65,7 +65,7 @@ The [accumulo-env.sh] file sets up environment variables needed by Accumulo:
    them to your `CLASSPATH` variable. If you you are running a vendor-specific release of
    Hadoop or Zookeeper, you may need to modify how the `CLASSPATH` variable is built in
    [accumulo-env.sh]. If Accumulo has problems loading classes when you start it, run 
-   `accumulo classpath -d` to debug and print Accumulo's classpath.
+   `accumulo classpath` to print Accumulo's classpath.
 
 2. Accumulo tablet servers are configured by default to use 1GB of memory (768MB is allocated
to
    JVM and 256MB is allocated for native maps). Native maps are allocated memory equal to
33% of


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message