* The SolrInputDocument instance. *

* Whether to overwrite existing document or not. If FALSE there will be duplicates (several documents with * the same ID). *

* Number of milliseconds within which to auto commit this document. Available since Solr 1.4 . Default (0) means * disabled. *

* When this value specified, it leaves the control of when to do the commit to Solr itself, optimizing number of * commits to a minimum while still fulfilling the update latency requirements, and Solr will automatically do a * commit when the oldest add in the buffer is due. *

* Returns a SolrUpdateResponse object or throws an Exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* An array containing the collection of SolrInputDocument instances. This array must be an actual variable. *

* Whether to overwrite existing document or not. If FALSE there will be duplicates (several documents with * the same ID). *

* Number of milliseconds within which to auto commit this document. Available since Solr 1.4 . Default (0) means * disabled. *

* When this value specified, it leaves the control of when to do the commit to Solr itself, optimizing number of * commits to a minimum while still fulfilling the update latency requirements, and Solr will automatically do a * commit when the oldest add in the buffer is due. *

* Returns a SolrUpdateResponse object or throws an Exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* This will refresh the 'view' of the index in a more performant manner, but without "on-disk" guarantees. * (Solr4.0+) *

* A soft commit is much faster since it only makes index changes visible and does not fsync index files or write a * new index descriptor. If the JVM crashes or there is a loss of power, changes that occurred after the last hard * commit will be lost. Search collections that have near-real-time requirements (that want index changes to be * quickly visible to searches) will want to soft commit often but hard commit less frequently. *

* block until a new searcher is opened and registered as the main query searcher, making the changes visible. *

* Merge segments with deletes away. (Solr1.4+) *

* Returns a SolrUpdateResponse object or throws an Exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* This is an array containing one of the following keys : *

*
• secure: (Boolean value indicating whether or not to connect in secure mode)
*
• hostname: (The hostname for the Solr server)
*
• port: (The port number)
*
• path: (The path to solr)
*
• wt: (The name of the response writer e.g. xml, json)
*
• login: (The username used for HTTP Authentication, if any)
*
• password: (The HTTP Authentication password)
*
• proxy_host: (The hostname for the proxy server, if any)
*
• proxy_port: (The proxy port)
*
• proxy_login: (The proxy username)
*
• proxy_password: (The proxy password)
*
• timeout: (This is maximum time in seconds allowed for the http data transfer operation. Default is 30 * seconds)
*
• ssl_cert: (File name to a PEM-formatted file containing the private key + private certificate * (concatenated in that order) )
*
• ssl_key: (File name to a PEM-formatted private key file only)
*
• ssl_keypassword: (Password for private key)
*
• ssl_cainfo: (Name of file holding one or more CA certificates to verify peer with)
*
• ssl_capath: (Name of directory holding multiple CA certificates to verify peer with )
*

* Please note the if the ssl_cert file only contains the private certificate, you have to specify a separate * ssl_key file. *

* The ssl_keypassword option is required if the ssl_cert or ssl_key options are set. *

* The value of the uniqueKey field declared in the schema *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* An array of IDs representing the uniqueKey field declared in the schema for each document to be deleted. This * must be an actual php variable. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* The array of queries. This must be an actual php variable. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* The query *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* Document ID *

* Document ids *

* Returns a string on success and null if there is nothing to return. *

* Returns an array containing all the options for the SolrClient object set internally. *

* Optimizes down to at most this number of segments. Since Solr 1.3 *

* This will refresh the 'view' of the index in a more performant manner, but without "on-disk" guarantees. * (Solr4.0+) *

* Block until a new searcher is opened and registered as the main query searcher, making the changes visible. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* Returns a SolrPingResponse object on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* A SolrParams object. It is recommended to use SolrQuery for advanced queries. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* An XML string with the raw request to the server. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrIllegalArgumentException if raw_request was an empty string. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* Returns a SolrUpdateResponse on success and throws an exception on failure. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* One of the following: *

*
• json
*
• phps
*
• xml
*

* One of the following : *

*
• SolrClient::SEARCH_SERVLET_TYPE
*
• SolrClient::UPDATE_SERVLET_TYPE
*
• SolrClient::THREADS_SERVLET_TYPE
*
• SolrClient::PING_SERVLET_TYPE
*
• SolrClient::TERMS_SERVLET_TYPE
*

* The new value for the servlet *

* Returns TRUE on success or FALSE on failure. *

* Returns a SolrGenericResponse object on success. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *

* Returns a SolrGenericResponse object on success. *

* Throws SolrClientException if the client had failed, or there was a connection issue. *

* Throws SolrServerException if the Solr Server had failed to satisfy the request. *