      - parameter environmentID: The ID of the environment.
      - parameter collectionID: The ID of the collection.
      - parameter documentID: The ID of the document.
-     - parameter file: The content of the document to ingest. The maximum supported file size is 50 megabytes. Files larger than 50 megabytes is rejected.
-     - parameter metadata: If you're using the Data Crawler to upload your documents, you can test a document against the type of metadata that the Data Crawler might send. The maximum supported metadata file size is 1 MB. Metadata parts larger than 1 MB are rejected. Example:  ``` {   \"Creator\": \"Johnny Appleseed\",   \"Subject\": \"Apples\" } ```.
+     - parameter file: The content of the document to ingest. The maximum supported file size is 50 megabytes. Files larger than 50
+     megabytes is rejected.
+     - parameter metadata: If you're using the Data Crawler to upload your documents, you can test a document against the type of metadata
+     that the Data Crawler might send. The maximum supported metadata file size is 1 MB. Metadata parts larger than 1 MB
+     are rejected. Example:  ``` {   \"Creator\": \"Johnny Appleseed\",   \"Subject\": \"Apples\" } ```.
      - parameter fileContentType: The content type of file.
      - parameter failure: A function executed if an error occurs.
      - parameter success: A function executed with the successful result.


     - parameter environmentID: The ID of the environment.
     - parameter configurationID: The ID of the configuration.
     - parameter configuration: Input an object that enables you to update and customize how your data is ingested and what enrichments are added to your data.  The `name` parameter is required and must be unique within the current `environment`. All other properties are optional, but if they are omitted  the default values replace the current value of each omitted property.  If the input configuration contains the `configuration_id`, `created`, or `updated` properties, they are ignored and overridden by the system, and an error is not returned so that the overridden fields do not need to be removed when updating a configuration.   The configuration can contain unrecognized JSON fields. Any such fields are ignored and do not generate an error. This makes it easier to use newer configuration files with older versions of the API and the service. It also makes it possible for the tooling to add additional metadata and information to the configuration.
     - parameter failure: A function executed if an error occurs.
     - parameter success: A function executed with the successful result.
     */


     - parameter environmentID: The ID of the environment.
     - parameter collectionID: The ID of the collection.
     - parameter expansions: An array of query expansion definitions.    Each object in the `expansions` array represents a term or set of terms
     that will be expanded into other terms. Each expansion object can be configured so that all terms are expanded to
     all other terms in the object - bi-directional, or a set list of terms can be expanded into a second list of terms
     - uni-directional.   To create a bi-directional expansion specify an `expanded_terms` array. When found in a query,
     all items in the `expanded_terms` array are then expanded to the other items in the same array.   To create a
     uni-directional expansion, specify both an array of `input_terms` and an array of `expanded_terms`. When items in
     the `input_terms` array are present in a query, they are expanded using the items listed in the `expanded_terms`
     array.
     - parameter failure: A function executed if an error occurs.
     - parameter success: A function executed with the successful result.
     */
