Apache Solr Reference Guide Covering Apache Solr 6.0

The value of a "delete" can be an array which contains a list of zero or more id's to be deleted. It is not a range
(start and end).
You can also specify _version_ with each "delete":
{
}
"delete":"id":50,
"_version_":12345
You can specify the version of deletes in the body of the update request as well.
JSON Update Convenience Paths
In addition to the /update handler, there are a few additional JSON specific request handler paths available by
default in Solr, that implicitly override the behavior of some request parameters:
Path
/update/json
/update/json/docs
Default Parameters
stream.contentType=application/json
stream.contentType=application/json
json.command=false
The /update/json path may be useful for clients sending in JSON formatted update commands from
applications where setting the Content-Type proves difficult, while the /update/json/docs path can be
particularly convenient for clients that always want to send in documents – either individually or as a list – with
out needing to worry about the full JSON command syntax.
Transforming and Indexing Custom JSON
If you have JSON documents that you would like to index without transforming them into Solr's structure, you can
add them to Solr by including some parameters with the update request. These parameters provide information
on how to split a single JSON file into multiple Solr documents and how to map fields to Solr's schema. One or
more valid JSON documents can be sent to the /update/json/docs path with the configuration params.
Mapping Parameters
These parameters allow you to define how a JSON file should be read for multiple Solr documents.
split: Defines the path at which to split the input JSON into multiple Solr documents and is required if you
have multiple documents in a single JSON file. If the entire JSON makes a single solr document, the path
must be “/”.
f: This is a multivalued mapping parameter. At least one field mapping must be provided. The format of
the parameter is target-field-name:json-path. The json-path is required. The target-field
-name is the Solr document field name, and is optional. If not specified, it is automatically derived from the
input JSON. Wildcards can be used here, see the section Wildcards below for more information.
mapUniqueKeyOnly (boolean): This parameter is particularly convenient when the fields in the input
JSON are not available in the schema and schemaless mode is not enabled. This will index all the fields
into the default search field (using the df parameter, below) and only the uniqueKey field is mapped to
the corresponding field in the schema. If the input JSON does not have a value for the uniqueKey field
then a UUID is generated for the same.
df: If the mapUniqueKeyOnly flag is used, the update handler needs a field where the data should be
indexed to. This is the same field that other handlers use as a default search field.
srcField: This is the name of the field to which the JSON source will be stored into. This can only be used
Apache Solr Reference Guide 6.0
190