anchor.diff:  // tag::contribute[]
   == How to contribute
   
  -. Fork this repo i.e. <username|organization>/hadoop-solr, following the http://help.github.com/fork-a-repo/[fork a repo/] tutorial. Then, clone the forked repo on your local machine:
  +. Fork this repo i.e. <username|organization>/hadoop-solr, following the http://help.github.com/fork-a-repo/[fork a repo] tutorial. Then, clone the forked repo on your local machine:
   +
   [source, git]
   $ git clone https://github.com/<username|organization>/hadoop-solr.git
  
positive.code: // tag::use-pig[]
  == Using the Functions
  
  There are two approaches to using functions in Pig: to `REGISTER` them in the script, or to load them with your Pig command line request.
  
  If using `REGISTER`, the Pig function jars must be put in HDFS in order to be used by your Pig script. It can be located anywhere in HDFS; you can either supply the path in your script or use a variable and define the variable with `-p` property definition.
  
  The example below uses the second approach, loading the .jars with `-Dpig.additional.jars` system property when launching the script. With this approach, the .jars can be located anywhere on the machine where the script will be run.
  
  When using the Pig functions, you can pass parameters for your script on the command line. The properties you will need to pass are the location of Solr and the collection to use; these are shown in detail in the example below.
  
  //end::use-pig[]
  
  // tag::kerberos-pig[]
  
  === Indexing to a Kerberos-Secured Solr Cluster
  
  When a Solr cluster is secured with Kerberos for internode communication, Pig scripts must include the full path to a JAAS file that includes the service principal and the path to a keytab file that will be used to index the output of the script to Solr.
  
  
negative.code: ====
  The `zkhost` parameter above is only used if you are indexing to a SolrCloud cluster, which uses ZooKeeper to route indexing and query requests.
  
  If, however, you are not using SolrCloud, you can use the `solrUrl` parameter, which takes the location of a standalone Solr instance, in the form of `\http://host:port/solr`.
  
  In the script, you would change the line that maps `solr.zkhost` to the `zkhost` property to map `solr.server.url` to the `solrUrl` property. For example:
  
  