Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B5DF3200BE3 for ; Wed, 7 Dec 2016 23:11:21 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B28DD160B0C; Wed, 7 Dec 2016 22:11:21 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 14615160B26 for ; Wed, 7 Dec 2016 23:11:18 +0100 (CET) Received: (qmail 57334 invoked by uid 500); 7 Dec 2016 22:11:18 -0000 Mailing-List: contact commits-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list commits@hbase.apache.org Received: (qmail 57090 invoked by uid 99); 7 Dec 2016 22:11:18 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Dec 2016 22:11:18 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id CAB42F2142; Wed, 7 Dec 2016 22:11:17 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: stack@apache.org To: commits@hbase.apache.org Date: Wed, 07 Dec 2016 22:11:21 -0000 Message-Id: <372fc22ceb7944858056a52348c681b6@git.apache.org> In-Reply-To: <8014a69194ae4c05b5e57e9df2b43daa@git.apache.org> References: <8014a69194ae4c05b5e57e9df2b43daa@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [5/8] hbase-site git commit: Published site at 6f25f838c0af80d2deaec91ed13248ce5024bd29. archived-at: Wed, 07 Dec 2016 22:11:21 -0000 http://git-wip-us.apache.org/repos/asf/hbase-site/blob/4ac23c25/apache_hbase_reference_guide.pdfmarks ---------------------------------------------------------------------- diff --git a/apache_hbase_reference_guide.pdfmarks b/apache_hbase_reference_guide.pdfmarks index 4ff8b03..6fbd5cc 100644 --- a/apache_hbase_reference_guide.pdfmarks +++ b/apache_hbase_reference_guide.pdfmarks @@ -2,8 +2,8 @@ /Author (Apache HBase Team) /Subject () /Keywords () - /ModDate (D:20161207142356) - /CreationDate (D:20161207142356) + /ModDate (D:20161207204746) + /CreationDate (D:20161207204746) /Creator (Asciidoctor PDF 1.5.0.alpha.6, based on Prawn 1.2.1) /Producer () /DOCINFO pdfmark http://git-wip-us.apache.org/repos/asf/hbase-site/blob/4ac23c25/book.html ---------------------------------------------------------------------- diff --git a/book.html b/book.html index 897eac8..f8bb073 100644 --- a/book.html +++ b/book.html @@ -429,7 +429,7 @@ such features or use patterns.

1. Introduction

-

Quickstart will get you up and running on a single-node, standalone instance of HBase, followed by a pseudo-distributed single-machine instance, and finally a fully-distributed cluster.

+

Quickstart will get you up and running on a single-node, standalone instance of HBase.

@@ -437,31 +437,16 @@ such features or use patterns.

2. Quick Start - Standalone HBase

-

This guide describes the setup of a standalone HBase instance running against the local filesystem. -This is not an appropriate configuration for a production instance of HBase, but will allow you to experiment with HBase. -This section shows you how to create a table in HBase using the hbase shell CLI, insert rows into the table, perform put and scan operations against the table, enable or disable the table, and start and stop HBase. -Apart from downloading HBase, this procedure should take less than 10 minutes.

-
-
- - - - - -
- - -
Local Filesystem and Durability
-The following is fixed in HBase 0.98.3 and beyond. See HBASE-11272 and HBASE-11218. -
+

This section describes the setup of a single-node standalone HBase. +A standalone instance has all HBase daemons — the Master, RegionServers, +and ZooKeeper — running in a single JVM persisting to the local filesystem. +It is our most basic deploy profile. We will show you how +to create a table in HBase using the hbase shell CLI, +insert rows into the table, perform put and scan operations against the +table, enable or disable the table, and start and stop HBase.

-

Using HBase with a local filesystem does not guarantee durability. -The HDFS local filesystem implementation will lose edits if files are not properly closed. -This is very likely to happen when you are experimenting with new software, starting and stopping the daemons often and not always cleanly. -You need to run HBase on HDFS to ensure all writes are preserved. -Running against the local filesystem is intended as a shortcut to get you familiar with how the general system works, as the very first phase of evaluation. -See HBASE-3696 and its associated issues for more details about the issues of running on the local filesystem.

+

Apart from downloading HBase, this procedure should take less than 10 minutes.

@@ -470,18 +455,11 @@ See HBASE-3696 an - -
-
Loopback IP - HBase 0.94.x and earlier
-The below advice is for hbase-0.94.x and older versions only. This is fixed in hbase-0.96.0 and beyond. -
-
-

Prior to HBase 0.94.x, HBase expected the loopback IP address to be 127.0.0.1. Ubuntu and some other distributions default to 127.0.1.1 and this will cause problems for you. See Why does HBase care about /etc/hosts? for detail

+

Prior to HBase 0.94.x, HBase expected the loopback IP address to be 127.0.0.1. +Ubuntu and some other distributions default to 127.0.1.1 and this will cause +problems for you. See Why does HBase care about /etc/hosts? for detail

-
-
Example 1. Example /etc/hosts File for Ubuntu
-

The following /etc/hosts file works correctly for HBase 0.94.x and earlier, on Ubuntu. Use this as a template if you run into trouble.

@@ -491,7 +469,12 @@ See HBASE-3696 an 127.0.0.1 ubuntu.ubuntu-domain ubuntu
+
+

This issue has been fixed in hbase-0.96.0 and beyond.

+ + +

2.1. JDK Version Requirements

@@ -503,17 +486,13 @@ See Java for information about supported JDK versions.

2.2. Get Started with HBase

-
Procedure: Download, Configure, and Start HBase
+
Procedure: Download, Configure, and Start HBase in Standalone Mode

  1. Choose a download site from this list of Apache Download Mirrors. Click on the suggested top link. -This will take you to a mirror of HBase -Releases. +This will take you to a mirror of HBase Releases. Click on the folder named stable and then download the binary file that ends in .tar.gz to your local filesystem. -Prior to 1.x version, be sure to choose the version that corresponds with the version of Hadoop you are -likely to use later (in most cases, you should choose the file for Hadoop 2, which will be called -something like hbase-0.98.13-hadoop2-bin.tar.gz). Do not download the file ending in src.tar.gz for now.

  2. @@ -526,10 +505,11 @@ $ cd hbase-2.0.0-SNAPSHOT/
  • -

    For HBase 0.98.5 and later, you are required to set the JAVA_HOME environment variable before starting HBase. -Prior to 0.98.5, HBase attempted to detect the location of Java if the variables was not set. -You can set the variable via your operating system’s usual mechanism, but HBase provides a central mechanism, conf/hbase-env.sh. -Edit this file, uncomment the line starting with JAVA_HOME, and set it to the appropriate location for your operating system. +

    You are required to set the JAVA_HOME environment variable before starting HBase. +You can set the variable via your operating system’s usual mechanism, but HBase +provides a central mechanism, conf/hbase-env.sh. +Edit this file, uncomment the line starting with JAVA_HOME, and set it to the +appropriate location for your operating system. The JAVA_HOME variable should be set to a directory which contains the executable file bin/java. Most modern Linux operating systems provide a mechanism, such as /usr/bin/alternatives on RHEL or CentOS, for transparently switching between versions of executables such as Java. In this case, you can set JAVA_HOME to the directory containing the symbolic link to bin/java, which is usually /usr.

    @@ -538,19 +518,6 @@ In this case, you can set JAVA_HOME to the directory containing the 
    JAVA_HOME=/usr
    • -
    - - - - - -
    - - -These instructions assume that each node of your cluster uses the same configuration. -If this is not the case, you may need to set JAVA_HOME separately for each node. -
    -

  • Edit conf/hbase-site.xml, which is the main HBase configuration file. @@ -560,7 +527,7 @@ Many servers are configured to delete the contents of /tmp upon reboot, The following configuration will store HBase’s data in the hbase directory, in the home directory of the user called testuser. Paste the <property> tags beneath the <configuration> tags, which should be empty in a new HBase install.

    -
    Example 2. Example hbase-site.xml for Standalone HBase
    +
    Example 1. Example hbase-site.xml for Standalone HBase
    @@ -580,8 +547,24 @@ Paste the <property> tags beneath the <configuration

    You do not need to create the HBase data directory. -HBase will do this for you. -If you create the directory, HBase will attempt to do a migration, which is not what you want.

    +HBase will do this for you. If you create the directory, +HBase will attempt to do a migration, which is not what you want.

    +
    +
    + + + + + +
    + + +The hbase.rootdir in the above example points to a directory +in the local filesystem. The 'file:/' prefix is how we denote local filesystem. +To home HBase on an existing instance of HDFS, set the hbase.rootdir to point at a +directory up on your instance: e.g. hdfs://namenode.example.org:8020/hbase. +For more on this variant, see the section below on Standalone HBase over HDFS. +
  • @@ -589,7 +572,8 @@ If you create the directory, HBase will attempt to do a migration, which is not Issue the command, and if all goes well, a message is logged to standard output showing that HBase started successfully. You can use the jps command to verify that you have one running process called HMaster. In standalone mode HBase runs all daemons within this single JVM, i.e. -the HMaster, a single HRegionServer, and the ZooKeeper daemon.

    +the HMaster, a single HRegionServer, and the ZooKeeper daemon. +Go to http://localhost:16010 to view the HBase Web UI.

    @@ -598,7 +582,10 @@ the HMaster, a single HRegionServer, and the ZooKeeper daemon.

    Java needs to be installed and available. -If you get an error indicating that Java is not installed, but it is on your system, perhaps in a non-standard location, edit the conf/hbase-env.sh file and modify the JAVA_HOME setting to point to the directory that contains bin/java your system. +If you get an error indicating that Java is not installed, +but it is on your system, perhaps in a non-standard location, +edit the conf/hbase-env.sh file and modify the JAVA_HOME +setting to point to the directory that contains bin/java your system.
    @@ -781,13 +768,21 @@ Use the jps to be sure that the HMaster and HRegionServer processes
    • +
    +

    The above has shown you how to start and stop a standalone instance of HBase. +In the next sections we give a quick overview of other modes of hbase deploy.

    +
    -

    2.3. Intermediate - Pseudo-Distributed Local Install

    +

    2.3. Pseudo-Distributed Local Install

    -

    After working your way through quickstart, you can re-configure HBase to run in pseudo-distributed mode. -Pseudo-distributed mode means that HBase still runs completely on a single host, but each HBase daemon (HMaster, HRegionServer, and ZooKeeper) runs as a separate process. -By default, unless you configure the hbase.rootdir property as described in quickstart, your data is still stored in /tmp/. +

    After working your way through quickstart standalone mode, +you can re-configure HBase to run in pseudo-distributed mode. +Pseudo-distributed mode means that HBase still runs completely on a single host, +but each HBase daemon (HMaster, HRegionServer, and ZooKeeper) runs as a separate process: +in standalone mode all daemons ran in one jvm process/instance. +By default, unless you configure the hbase.rootdir property as described in +quickstart, your data is still stored in /tmp/. In this walk-through, we store your data in HDFS instead, assuming you have HDFS available. You can skip the HDFS configuration to continue storing your data in the local filesystem.

    @@ -1013,7 +1008,7 @@ The architecture will be as follows:

    This quickstart assumes that each node is a virtual machine and that they are all on the same network. -It builds upon the previous quickstart, Intermediate - Pseudo-Distributed Local Install, assuming that the system you configured in that procedure is now node-a. +It builds upon the previous quickstart, Pseudo-Distributed Local Install, assuming that the system you configured in that procedure is now node-a. Stop HBase on node-a before continuing.

    @@ -1198,7 +1193,7 @@ node-b.example.com: starting master, logging to /home/hbuser/hbase-0.98.3-hadoop You may see additional Java processes running on your servers as well, if they are used for other purposes.

    -
    Example 3. node-a jps Output
    +
    Example 2. node-a jps Output
    @@ -1211,7 +1206,7 @@ You may see additional Java processes running on your servers as well, if they a
    -
    Example 4. node-b jps Output
    +
    Example 3. node-b jps Output
    @@ -1225,7 +1220,7 @@ You may see additional Java processes running on your servers as well, if they a
    -
    Example 5. node-a jps Output
    +
    Example 4. node-a jps Output
    @@ -1534,7 +1529,7 @@ See Loopback IP for more details.

    Configuring the maximum number of file descriptors and processes for the user who is running the HBase process is an operating system configuration, rather than an HBase configuration. It is also important to be sure that the settings are changed for the user that actually runs HBase. To see which user started HBase, and that user’s ulimit configuration, look at the first line of the HBase log for that instance. A useful read setting config on your hadoop cluster is Aaron Kimball’s Configuration Parameters: What can you just ignore?

    -
    Example 6. ulimit Settings on Ubuntu
    +
    Example 5. ulimit Settings on Ubuntu

    To configure ulimit settings on Ubuntu, edit /etc/security/limits.conf, which is a space-delimited file with four columns. Refer to the man page for limits.conf for details about the format of this file. In the following example, the first line sets both soft and hard limits for the number of open files (nofile) to 32768 for the operating system user with the username hadoop. The second line sets the number of processes to 32000 for the same user.

    @@ -1976,6 +1971,40 @@ Standalone mode is what is described in the quickstart In standalone mode, HBase does not use HDFS — it uses the local filesystem instead — and it runs all HBase daemons and a local ZooKeeper all up in the same JVM. ZooKeeper binds to a well known port so clients may talk to HBase.

    +
    +

    5.1.1. Standalone HBase over HDFS

    +
    +

    A sometimes useful variation on standalone hbase has all daemons running inside the +one JVM but rather than persist to the local filesystem, instead +they persist to an HDFS instance.

    +
    +
    +

    You might consider this profile when you are intent on +a simple deploy profile, the loading is light, but the +data must persist across node comings and goings. Writing to +HDFS where data is replicated ensures the latter.

    +
    +
    +

    To configure this standalone variant, edit your hbase-site.xml +setting the hbase.rootdir to point at a directory in your +HDFS instance but then set hbase.cluster.distributed +to false. For example:

    +
    +
    +
    +
    <configuration>
+  <property>
+    <name>hbase.rootdir</name>
+    <value>hdfs://namenode.example.org:8020/hbase</value>
+  </property>
+  <property>
+    <name>hbase.cluster.distributed</name>
+    <value>false</value>
+  </property>
+</configuration>
    +
    +
    +

    5.2. Distributed

    @@ -2042,7 +2071,7 @@ All hosts listed in this file will have their RegionServer processes started and

    See the ZooKeeper section for ZooKeeper setup instructions for HBase.

    -
    Example 7. Example Distributed HBase Cluster
    +
    Example 6. Example Distributed HBase Cluster

    This is a bare-bones conf/hbase-site.xml for a distributed HBase cluster. @@ -6585,7 +6614,7 @@ Spawning HBase Shell commands in this way is slow, so keep that in mind when you

    -
    Example 8. Passing Commands to the HBase Shell
    +
    Example 7. Passing Commands to the HBase Shell

    You can pass commands to the HBase Shell in non-interactive mode (see hbase.shell.noninteractive) using the echo command and the | (pipe) operator. @@ -6621,7 +6650,7 @@ DESCRIPTION ENABLED

    -
    Example 9. Checking the Result of a Scripted Command
    +
    Example 8. Checking the Result of a Scripted Command

    Since scripts are not designed to be run interactively, you need a way to check whether your command failed or succeeded. @@ -6669,7 +6698,7 @@ For instance, if your script creates a table, but returns a non-zero exit value,

    You can enter HBase Shell commands into a text file, one command per line, and pass that file to the HBase Shell.

    -
    Example 10. Example Command File
    +
    Example 9. Example Command File
    @@ -6688,7 +6717,7 @@ enable 'test'
    -
    Example 11. Directing HBase Shell to Execute the Commands
    +
    Example 10. Directing HBase Shell to Execute the Commands

    Pass the path to the command file as the only argument to the hbase shell command. @@ -7319,7 +7348,7 @@ Namespace membership is determined during table creation by specifying a fully-q

    -
    Example 12. Examples
    +
    Example 11. Examples
    @@ -7364,7 +7393,7 @@ alter_namespace 'my_ns', {METHOD => 'set', 'PROPERTY_NAME' => 'PROPERTY_VA
    -
    Example 13. Examples
    +
    Example 12. Examples
    @@ -7537,7 +7566,7 @@ This section is basically a synopsis of this article by Bruno Dumon.

    Prior to HBase 0.96, the default number of versions kept was 3, but in 0.96 and newer has been changed to 1.

    -
    Example 14. Modify the Maximum Number of Versions for a Column Family
    +
    Example 13. Modify the Maximum Number of Versions for a Column Family

    This example uses HBase Shell to keep a maximum of 5 versions of all columns in column family f1. @@ -7551,7 +7580,7 @@ You could also use -

    Example 15. Modify the Minimum Number of Versions for a Column Family
    +
    Example 14. Modify the Minimum Number of Versions for a Column Family

    You can also specify the minimum number of versions to store per column family. @@ -8008,7 +8037,7 @@ Salting can be helpful if you have a few "hot" row key patterns which come up ov Consider the following example, which shows that salting can spread write load across multiple RegionServers, and illustrates some of the negative implications for reads.

    -
    Example 16. Salting Example
    +
    Example 15. Salting Example

    Suppose you have the following list of row keys, and your table is split such that there is one region for each letter of the alphabet. @@ -8063,7 +8092,7 @@ In this way, salting attempts to increase throughput on writes, but has a cost d Using a deterministic hash allows the client to reconstruct the complete rowkey and use a Get operation to retrieve that row as normal.

    -
    Example 17. Hashing Example
    +
    Example 16. Hashing Example
    Given the same situation in the salting example above, you could instead apply a one-way hash that would cause the row with key foo0003 to always, and predictably, receive the a prefix. Then, to retrieve that row, you would already know the key. @@ -8424,7 +8453,7 @@ This allows for point-in-time queries even in the presence of deletes.

    A new "raw" scan options returns all deleted rows and the delete markers.

    -
    Example 18. Change the Value of KEEP_DELETED_CELLS Using HBase Shell
    +
    Example 17. Change the Value of KEEP_DELETED_CELLS Using HBase Shell
    @@ -8434,7 +8463,7 @@ A new "raw" scan options returns all deleted rows and the delete markers.

    -
    Example 19. Change the Value of KEEP_DELETED_CELLS Using the API
    +
    Example 18. Change the Value of KEEP_DELETED_CELLS Using the API
    @@ -11667,7 +11696,7 @@ The correct way to apply cell level permissions is to do so in the application c This means that cell ACLs do not override ACLs at less granularity.

    -
    Example 20. HBase Shell
    +
    Example 19. HBase Shell
      @@ -11758,7 +11787,7 @@ For some examples of scanner specifications, issue the following HBase Shell com
    -
    Example 21. API
    +
    Example 20. API

    The following example shows how to grant access at the table level.

    @@ -11833,7 +11862,7 @@ The correct way to apply cell-level permissions is to do so in the application c
    -
    Example 22. Revoking Access To a Table
    +
    Example 21. Revoking Access To a Table
    @@ -11866,7 +11895,7 @@ The correct way to apply cell-level permissions is to do so in the application c

  • Showing a User’s Effective Permissions

    -
    Example 23. HBase Shell
    +
    Example 22. HBase Shell
    @@ -11883,7 +11912,7 @@ hbase> user_permission JAVA_REGEX
    -
    Example 24. API
    +
    Example 23. API
    @@ -12102,7 +12131,7 @@ Refer to the official API for usage instructions.

  • Define the List of Visibility Labels

    -
    Example 25. HBase Shell
    +
    Example 24. HBase Shell
    @@ -12112,7 +12141,7 @@ Refer to the official API for usage instructions.

    -
    Example 26. Java API
    +
    Example 25. Java API
    @@ -12139,7 +12168,7 @@ Refer to the official API for usage instructions.

  • Associate Labels with Users

    -
    Example 27. HBase Shell
    +
    Example 26. HBase Shell
    @@ -12164,7 +12193,7 @@ Refer to the official API for usage instructions.

    -
    Example 28. Java API
    +
    Example 27. Java API
    @@ -12188,7 +12217,7 @@ Refer to the official API for usage instructions.

  • Clear Labels From Users

    -
    Example 29. HBase Shell
    +
    Example 28. HBase Shell
    @@ -12213,7 +12242,7 @@ Refer to the official API for usage instructions.

    -
    Example 30. Java API
    +
    Example 29. Java API
    @@ -12238,7 +12267,7 @@ VisibilityLabelsResponse response = null
    -
    Example 31. HBase Shell
    +
    Example 30. HBase Shell
    @@ -12271,7 +12300,7 @@ The correct way to apply cell level labels is to do so in the application code w
    -
    Example 32. Java API
    +
    Example 31. Java API
    @@ -12323,7 +12352,7 @@ set as an additional filter. It will further filter your results, rather than giving you additional authorization.

    -
    Example 33. HBase Shell
    +
    Example 32. HBase Shell
    @@ -12334,7 +12363,7 @@ hbase> scan 'table1', AUTHORIZATIONS => ['private']
    -
    Example 34. Java API
    +
    Example 33. Java API
    @@ -12707,7 +12736,7 @@ HBase manages creation and deletion of this directory.

    All options have been discussed separately in the sections above.

    -
    Example 35. Example Security Settings in hbase-site.xml
    +
    Example 34. Example Security Settings in hbase-site.xml
    @@ -12799,7 +12828,7 @@ All options have been discussed separately in the sections above.

    -
    Example 36. Example Group Mapper in Hadoop core-site.xml
    +
    Example 35. Example Group Mapper in Hadoop core-site.xml

    Adjust these settings to suit your environment.

    @@ -13127,7 +13156,7 @@ HTable table2 = new HTable(conf2, -
    Example 37. Pre-Creating a Connection
    +
    Example 36. Pre-Creating a Connection
    @@ -16947,7 +16976,7 @@ an object is considered to be a MOB. Only IS_MOB is required. If yo specify the MOB_THRESHOLD, the default threshold value of 100 KB is used.

    -
    Example 38. Configure a Column for MOB Using HBase Shell
    +
    Example 37. Configure a Column for MOB Using HBase Shell
    @@ -16958,7 +16987,7 @@ hbase> alter 't1', {NAME => 'f1', IS_MOB => true, MOB_THRESHOLD => 1
    -
    Example 39. Configure a Column for MOB Using the Java API
    +
    Example 38. Configure a Column for MOB Using the Java API
    @@ -17014,7 +17043,7 @@ the following properties to the RegionServer’s hbase-site.xml suit your environment, and restart or rolling restart the RegionServer.

    -
    Example 40. Example MOB Cache Configuration
    +
    Example 39. Example MOB Cache Configuration
    @@ -17177,7 +17206,7 @@ See Apache HBase External APIs for more information

    75. Examples

    -
    Example 41. Create, modify and delete a Table Using Java
    +
    Example 40. Create, modify and delete a Table Using Java
    @@ -18013,7 +18042,7 @@ represent persistent data.

    Download the code from http://code.google.com/p/hbase-jdo/.

    -
    Example 42. JDO Example
    +
    Example 41. JDO Example

    This example uses JDO to create a table and an index, insert a row into a table, get @@ -18257,7 +18286,7 @@ $ bin/hbase org.python.util.jython

    81.2. Jython Code Examples

    -
    Example 43. Table Creation, Population, Get, and Delete with Jython
    +
    Example 42. Table Creation, Population, Get, and Delete with Jython

    The following Jython code example creates a table, populates it with data, fetches @@ -18314,7 +18343,7 @@ admin.deleteTable(desc.getName())

    -
    Example 44. Table Scan Using Jython
    +
    Example 43. Table Scan Using Jython

    This example scans a table and returns the results that match a given family qualifier.

    @@ -18438,7 +18467,7 @@ If single quotes are present in the argument, they must be escaped by an additio
    -
    Example 45. Compound Operators
    +
    Example 44. Compound Operators

    You can combine multiple operators to create a hierarchy of filters, such as the following example:

    @@ -18467,7 +18496,7 @@ If single quotes are present in the argument, they must be escaped by an additio
    -
    Example 46. Precedence Example
    +
    Example 45. Precedence Example
    @@ -18826,7 +18855,7 @@ Executor as a multi-threaded client application. This allows any Spark Tasks running on the executors to access the shared Connection object.

    -
    Example 47. HBaseContext Usage Example
    +
    Example 46. HBaseContext Usage Example

    This example shows how HBaseContext can be used to do a foreachPartition on a RDD @@ -18988,7 +19017,7 @@ access to HBase

    -
    Example 48. bulkPut Example with DStreams
    +
    Example 47. bulkPut Example with DStreams

    Below is an example of bulkPut with DStreams. It is very close in feel to the RDD @@ -19063,7 +19092,7 @@ out directly from the reduce phase.

    First lets look at an example of using the basic bulk load functionality

    -
    Example 49. Bulk Loading Example
    +
    Example 48. Bulk Loading Example

    The following example shows bulk loading with Spark.

    @@ -19143,7 +19172,7 @@ to load the newly created HFiles into HBase.

    -
    Example 50. Using Additional Parameters
    +
    Example 49. Using Additional Parameters
    @@ -19191,7 +19220,7 @@ load.doBulkLoad(new Path(stagingFolder.getPath),

    Now lets look at how you would call the thin record bulk load implementation

    -
    Example 51. Using thin record bulk load
    +
    Example 50. Using thin record bulk load
    @@ -19396,7 +19425,7 @@ The lifetime of this temporary table is tied to the SQLContext that was used to

    86.6. Others

    -
    Example 52. Query with different timestamps
    +
    Example 51. Query with different timestamps

    In HBaseSparkConf, four parameters related to timestamp can be set. They are TIMESTAMP, @@ -19443,7 +19472,7 @@ sqlContext.sql("select count(col1) from table").show

    -
    Example 53. Native Avro support
    +
    Example 52. Native Avro support

    HBase-Spark Connector support different data formats like Avro, Jason, etc. The use case below @@ -20953,7 +20982,7 @@ It is useful for tuning the IO impact of prefetching versus the time before all

    To enable prefetching on a given column family, you can use HBase Shell or use the API.

    -
    Example 54. Enable Prefetch Using HBase Shell
    +
    Example 53. Enable Prefetch Using HBase Shell
    @@ -20963,7 +20992,7 @@ It is useful for tuning the IO impact of prefetching versus the time before all
    -
    Example 55. Enable Prefetch Using the API
    +
    Example 54. Enable Prefetch Using the API
    @@ -21738,7 +21767,7 @@ If this is set to 0 (the default), hedged reads are disabled.

    -
    Example 56. Hedged Reads Configuration Example
    +
    Example 55. Hedged Reads Configuration Example
    @@ -22960,7 +22989,7 @@ remember that WALs are saved when replication is disabled, as long as there are

    115.2. Loopback IP

    HBase expects the loopback IP Address to be 127.0.0.1. -See the Getting Started section on Loopback IP - HBase 0.94.x and earlier.

    +See the Getting Started section on [loopback.ip].

    @@ -24270,7 +24299,7 @@ exit code.

    -
    Example 57. Canary in a Kerberos-Enabled Cluster
    +
    Example 56. Canary in a Kerberos-Enabled Cluster

    This example shows each of the properties with valid values.

    @@ -25154,7 +25183,7 @@ The script requires you to set some environment variables before running it. Examine the script and modify it to suit your needs.

    -
    Example 58. rolling-restart.sh General Usage
    +
    Example 57. rolling-restart.sh General Usage
    @@ -27319,7 +27348,7 @@ If it’s either a new feature request, enhancement, or a bug, file a ticket
    -
    Example 59. Code Blocks in Jira Comments
    +
    Example 58. Code Blocks in Jira Comments

    A commonly used macro in Jira is {code}. Everything inside the tags is preformatted, as in this example.

    @@ -27840,7 +27869,7 @@ For now, just be aware of the difference between HBase 1.x builds and those of H This difference is important to the build instructions.

    -
    Example 60. Example ~/.m2/settings.xml File
    +
    Example 59. Example ~/.m2/settings.xml File

    Publishing to maven requires you sign the artifacts you want to upload. @@ -29846,7 +29875,7 @@ This is the indication that the patch was not created with --no-prefix

    -
    Example 61. Example of Committing a Patch
    +
    Example 60. Example of Committing a Patch

    One thing you will notice with these examples is that there are a lot of git pull commands. @@ -33217,7 +33246,7 @@ You do not need to re-create the table or copy data. If you are changing codecs, be sure the old codec is still available until all the old StoreFiles have been compacted.

    -
    Example 62. Enabling Compression on a ColumnFamily of an Existing Table using HBaseShell
    +
    Example 61. Enabling Compression on a ColumnFamily of an Existing Table using HBaseShell
    @@ -33229,7 +33258,7 @@ hbase> enable 'test'
    -
    Example 63. Creating a New Table with Compression On a ColumnFamily
    +
    Example 62. Creating a New Table with Compression On a ColumnFamily
    @@ -33239,7 +33268,7 @@ hbase> enable 'test'
    -
    Example 64. Verifying a ColumnFamily’s Compression Settings
    +
    Example 63. Verifying a ColumnFamily’s Compression Settings
    @@ -33264,7 +33293,7 @@ DESCRIPTION ENABLED You must specify either -write or -update-read as your first parameter, and if you do not specify another parameter, usage advice is printed for each option.

    -
    Example 65. LoadTestTool Usage
    +
    Example 64. LoadTestTool Usage
    @@ -33324,7 +33353,7 @@ Options:
    -
    Example 66. Example Usage of LoadTestTool
    +
    Example 65. Example Usage of LoadTestTool
    @@ -33348,7 +33377,7 @@ Disable the table before altering its DATA_BLOCK_ENCODING setting. Following is an example using HBase Shell:

    -
    Example 67. Enable Data Block Encoding On a Table
    +
    Example 66. Enable Data Block Encoding On a Table
    @@ -33366,7 +33395,7 @@ hbase> enable 'test'
    -
    Example 68. Verifying a ColumnFamily’s Data Block Encoding
    +
    Example 67. Verifying a ColumnFamily’s Data Block Encoding
    http://git-wip-us.apache.org/repos/asf/hbase-site/blob/4ac23c25/devapidocs/constant-values.html ---------------------------------------------------------------------- diff --git a/devapidocs/constant-values.html b/devapidocs/constant-values.html index d74a5f7..7bc36b1 100644 --- a/devapidocs/constant-values.html +++ b/devapidocs/constant-values.html @@ -3716,14 +3716,14 @@ public static final String date -"Wed Dec 7 14:13:58 UTC 2016" +"Wed Dec 7 20:37:37 UTC 2016" public static final String revision -"61220e4d7c8d7e5fb8ed3bbe2469bc86632c48de" +"6f25f838c0af80d2deaec91ed13248ce5024bd29" http://git-wip-us.apache.org/repos/asf/hbase-site/blob/4ac23c25/devapidocs/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.ImplData.html ---------------------------------------------------------------------- diff --git a/devapidocs/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.ImplData.html b/devapidocs/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.ImplData.html index dae4f1c..d1bcacf 100644 --- a/devapidocs/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.ImplData.html +++ b/devapidocs/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.ImplData.html @@ -393,166 +393,166 @@ extends org.jamon.AbstractTemplateProxy.ImplData 
    private HMaster m_master
    • - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -598,247 +598,247 @@ extends org.jamon.AbstractTemplateProxy.ImplData 
    public HMaster getMaster()
    - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +