anchor.diff:       LOCATION '/tmp/solr' --<6>
        TBLPROPERTIES('solr.zkhost' = 'zknode1:2181,zknode2:2181,zknode3:2181/solr',
                      'solr.collection' = 'gettingstarted',
  -                   'solr.query' = '*:*'),
  -                   'lww.jaas.file' = '/data/jaas-client.conf'; --<7>
  +                   'solr.query' = '*:*'), --<7>
  +                   'lww.jaas.file' = '/data/jaas-client.conf'; --<8>
   
   
   INSERT OVERWRITE TABLE solr SELECT b.* FROM books b;
  
positive.code: * `solr-hive-serde/build/libs/{packageUser}-hive-serde-{connectorVersion}.jar`
  * `solr-hive-serde-0.13/build/libs/{packageUser}-hive-serde-0.13-{connectorVersion}.jar`
  
  === Troubleshooting
  
  If GitHub + SSH is not configured the following exception will be thrown:
  
  [source]
  ----
  
negative.code: 
  If the table needs to be dropped at a later time, you can use the DROP TABLE command in Hive. This will remove the metadata stored in the table in Hive, but will not modify the underlying data (in this case, the Solr index).
  
  // end::index-solr[]
  
  // tag::index-fusion[]
  ==== Indexing Data to Fusion
  If you use Lucidworks Fusion, you can index data from Hive to Solr via Fusion's index pipelines. These pipelines allow you several options for further transforming your data.
  
  [TIP]
  ====
  If you are using Fusion, you already have the Hive SerDe in Fusion's `./apps/connectors/resources/lucid.hadoop/jobs` directory. The SerDe jar that supports Fusion is v2.2.4 or higher. This was released with Fusion 3.0.
  
  A 2.2.4 or higher jar built from this repository will also work with Fusion 2.4.x releases.
  ====
  
  This is an example Hive command to create an external table to index documents in Fusion and to query the table later.
  
  [source,sql]
  hive> CREATE EXTERNAL TABLE fusion (id string, field1 string, field2 int)
        STORED BY 'com.lucidworks.hadoop.hive.FusionStorageHandler'
        LOCATION '/tmp/solr'
        TBLPROPERTIES('fusion.endpoints' = 'http://localhost:8764/api/apollo/index-pipelines/<pipeline>/collections/<collection>/index',
                      'fusion.realm' = 'KERBEROS',
                      'fusion.user' = 'fusion-indexer@FUSIONSERVER.COM',
                      'java.security.auth.login.config' = '/path/to/JAAS/file',
                      'fusion.jaas.appname' = 'FusionClient',);
                      'fusion.query.endpoints' = 'http://localhost:8764/api/apollo/query-pipelines/<pipeline>/collections/<collection>/<handler>/?',
                      'fusion.query' = '*:*'
  
  In this example, we have created an external table named "fusion", and defined a custom storage handler (`STORED BY 'com.lucidworks.hadoop.hive.FusionStorageHandler'`).
  
  Here are the details for each parameter in `TBLPROPERTIES`:
  
  `fusion.endpoints`::
  The full URL to the index pipeline in Fusion. The URL should include the pipeline name and the collection data will be indexed to.
  
  `fusion.realm`::
  This is used with `fusion.user` and `fusion.password` to authenticate to Fusion for indexing data. Two options are supported, `KERBEROS` or `NATIVE`.
  +
  Kerberos authentication is supported with the additional definition of a JAAS file. The properties `java.security.auth.login.config` and `fusion.jaas.appname` are used to define the location of the JAAS file and the section of the file to use.
  +
  Native authentication uses a Fusion-defined username and password. This user must exist in Fusion, and have the proper permissions to index documents.
  
  `fusion.user`::
  The Fusion username or Kerberos principal to use for authentication to Fusion. If a Fusion username is used (`'fusion.realm' = 'NATIVE'`), the `fusion.password` must also be supplied.
  
  `fusion.password`::
  This property is not shown in the example above. The password for the `fusion.user` when the `fusion.realm` is `NATIVE`.
  
  `java.security.auth.login.config`::
  This property defines the path to a JAAS file that contains a service principal and keytab location for a user who is authorized to read from and write to Fusion and Hive.
  +
  The JAAS configuration file *must* be copied to the same path on every node where a Node Manager is running (i.e., every node where map/reduce tasks are executed). Here is a sample section of a JAAS file:
  +
  [source]
  Client { --<1>
    com.sun.security.auth.module.Krb5LoginModule required
    useKeyTab=true
    keyTab="/data/fusion-indexer.keytab" --<2>
    storeKey=true
    useTicketCache=true
    debug=true
    principal="fusion-indexer@FUSIONSERVER.COM"; --<3>
  };
  +
  <1> The name of this section of the JAAS file. This name will be used with the `fusion.jaas.appname` parameter.
  <2> The location of the keytab file.
  <3> The service principal name. This should be a different principal than the one used for Fusion, but must have access to both Fusion and Hive. This name is used with the `fusion.user` parameter described above.
  
  `fusion.jaas.appname`::
  Used only when indexing to or reading from Fusion when it is secured with Kerberos.
  +
  This property provides the name of the section in the JAAS file that includes the correct service principal and keytab path.
  
  `fusion.query.endpoints`::
  The full URL to a query pipeline in Fusion. The URL should include the pipeline name and the collection data will be read from. You should also specify the request handler to be used.
  +
  If you do not intend to query your Fusion data from Hive, you can skip this parameter.
  
  `fusion.query`::
  The query to run in Fusion to select records to be read into Hive. This is `\*:*` by default, which selects all records in the index.
  +
  If you do not intend to query your Fusion data from Hive, you can skip this parameter.
  
  // end::index-fusion[]
  
  
  // tag::query-hive[]
  === Query and Insert Data to Hive
  
  Once the table is configured, any syntactically correct Hive query will be able to query the index.
  
  For example, to select three fields named "id", "field1", and "field2" from the "solr" table, you would use a query such as:
  
  `hive> SELECT id, field1, field2 FROM solr;`
  
  Replace the table name as appropriate to use this example with your data.
  
  To join data from tables, you can make a request such as:
  
  