Rename master packages to manager. (#1904)

Rename master packages to manager.

This change renames all packages with 'master' in the name to 'manager'
with the exception of the o.a.a.core.master.thrift package. Due to the
usage of some of these classes in the user-facing TabletBalancer code
hierarchy, the renaming of this package will wait until the next major
release. While it would have been possible to rename the package for
most of the classes int he master.thrift package, then we would have
been left in a state where we could not re-generate the thrift classes
if that were needed.

The TableState enum, which is in a renamed package, is used in some
classes in the public API though it is not used in the public API
itself (i.e., it is not a parameter or return type for any public or
protected method in the public API). The usages are limited to internal
comparisons and lookup of enum values based on the string. Therefore,
this renaming won't break any clients.

* IDE refactoring was used to rename packages having master in their
  name to the same package name, but with master replaced by manager.
* Updated Property enums where the default implementation for the
  property was a class that got re-packaged. Kept a "compatibility"
  implementation for such classes, which is the class under the old
  package name extends the class under the new package name, is
  deprecated, is empty except for a constructor that logs a warning
  about the deprecation.
* Add "compatibility" classes for those in packages renamed that have
  a main method. The compatibility class extends the class in the new
  package name, and the main method delegates to the moved class' main
  method as well as logging a warning about the deprecation.

re #1642
203 files changed
tree: cb1452b3ee93ba2f42a3bebb90229c3a6b290882
  1. .github/
  2. assemble/
  3. contrib/
  4. core/
  5. hadoop-mapreduce/
  6. iterator-test-harness/
  7. minicluster/
  8. server/
  9. shell/
  10. src/
  11. start/
  12. test/
  13. .asf.yaml
  14. .gitignore
  15. CONTRIBUTING.md
  16. DEPENDENCIES
  17. LICENSE
  18. NOTICE
  19. pom.xml
  20. README.md
  21. TESTING.md
README.md

Apache Accumulo


Build Status Maven Central Javadoc Apache License

Apache Accumulo is a sorted, distributed key/value store that provides robust, scalable data storage and retrieval. With Apache Accumulo, users can store and manage large data sets across a cluster. Accumulo uses Apache Hadoop's HDFS to store its data and Apache Zookeeper for consensus. Check out the Accumulo project website for news and general information.

Getting Started

More resources can be found on the project website.

Building

Accumulo uses Maven to compile, test, and package its source. The following command will build the binary tar.gz from source. Add -DskipTests to build without waiting for the tests to run.

mvn package

This command produces assemble/target/accumulo-<version>-bin.tar.gz

Export Control


This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See https://www.wassenaar.org/ for more information.

The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.

The following provides more details on the included cryptographic software:

Apache Accumulo uses the built-in java cryptography libraries in its RFile encryption implementation. See oracle's export-regulations doc for more details for on Java‘s cryptography features. Apache Accumulo also uses the bouncycastle library for some cryptographic technology as well. See the BouncyCastle site for more details on bouncycastle’s cryptography features.