Deprecate input definitionn in docs

docs/api-reference.md

@@ -199,6 +199,10 @@ curl localhost:10101/index/repository/frame/stats/field/pullrequests \
 
 ### Create input definition
 
+<div class="warning">
+Input definition is deprecated as of v0.9.
+</div>
+
 `POST /index/<index-name>/input-definition/<input-definition-name>`
  
 Creates an input definition in the given index with the given name.
@@ -263,6 +267,10 @@ curl localhost:10101/index/user/input-definition/stargazer-input \
 
 ### Get input definition
 
+<div class="warning">
+Input definition is deprecated as of v0.9.
+</div>
+
 `GET /index/<index-name>/input-definition/<input-definition-name>`
 
 Returns the given input definition as JSON.
@@ -276,6 +284,10 @@ curl -XGET localhost:10101/index/user/input-definition/stargazer-input
 
 ### Remove input definition
 
+<div class="warning">
+Input definition is deprecated as of v0.9.
+</div>
+
 `DELETE /index/<index-name>/input-definition/<input-definition-name>`
 
 Removes the given input definition.
@@ -289,6 +301,10 @@ curl -XDELETE localhost:10101/index/user/input-definition/stargazer-input
 
 ### Process input data
 
+<div class="warning">
+Input definition is deprecated as of v0.9.
+</div>
+
 `POST /index/<index-name>/input/<input-definition-name>`
 
 Processes the JSON payload using the given input definition.

docs/getting-started.md

@@ -85,7 +85,7 @@ curl localhost:10101/index/repository/frame/language \
 
 #### Import Data From CSV Files
 
-If you import data using csv files and without input defintion, download the `stargazer.csv` and `language.csv` files in that repo.
+Download the `stargazer.csv` and `language.csv` files here:
 
 ```
 curl -O https://raw.githubusercontent.com/pilosa/getting-started/master/stargazer.csv
@@ -110,7 +110,12 @@ docker exec -it pilosa /pilosa import -i repository -f language /language.csv
 Note that, both the user IDs and the repository IDs were remapped to sequential integers in the data files, they don't correspond to actual Github IDs anymore. You can check out `languages.txt` to see the mapping for languages.
 
 ### Input Definition
-Alternatively Pilosa can import JSON data using an [Input Definition](../input-definition/) describing the schema and ETL rules to process the data.  
+
+<div class="warning">
+Input definition is deprecated as of v0.9.
+</div>
+
+Alternatively Pilosa can import JSON data using an [Input Definition](../input-definition/) describing the schema and ETL rules to process the data.
 
 #### Make Some Queries
 

docs/input-definition.md

@@ -1,64 +1,11 @@
 +++
 title = "Input Definition"
 weight = 8
-nav = [
-    "Create the Schema",
-    "Import Data",
-]
 +++
 
 ## Input Definition
-This document builds on the data import concepts introduced in [Getting Started](../getting-started/).  
-Here we will demonstrate creating the index's schema and data definition.  Then using this definition to import JSON data.
-
-### Create the Schema
-
-Input definitions allow users to define a schema based on their data and to provide data to Pilosa in a more standard format like JSON. Once an input definition is created, we can send data to Pilosa as JSON, and as long as the data adheres to the definition, Pilosa will internally perform all of the appropriate mutations.
-
-Before creating a schema, let's create the repository index first:
-
-```
-curl localhost:10101/index/repository -X POST
-```
-The sample input definition schema for the "Star Trace" project is at [Pilosa Getting Started repository](https://github.com/pilosa/getting-started) in the `input_definition.json` file. Download it using:
-```
-curl -OL https://github.com/pilosa/getting-started/raw/master/input_definition.json
-```
-
-Run the following to create the input definition:
-```
-curl localhost:10101/index/repository/input-definition/stargazer -d @input_definition.json 
-```
-
-Instead of creating a `stargazer` frame and a `language` frame individually like in [Getting Started](../getting-started/), we can create multiple frames in one input definition.
-We can also set `repo_id` for multiple frames at the same time by providing field actions. There are three options for valueDestination:
-
- - value-to-row: The value for this field is used as the `rowID`.
- - single-row-boolean: The value must be a boolean, and this specifies `SetBit()` or `ClearBit()`, a `rowID` must be specified for this destination type.
- - mapping: The value for this field is used to lookup a `rowID` in a map. A valueMap is required for this destination type.
- - set-timestamp: The value for this field is used to lookup timestamp and set timestamp for the whole frame
-
-### Import Data
-
-The sample data for the input definition we created above is in the `json_input.json` file at [Pilosa Getting Started repository](https://github.com/pilosa/getting-started). Download it using:
-```
-curl -OL https://github.com/pilosa/getting-started/raw/master/json_input.json
-```
-
-Then run the following to import it:
-```
-curl localhost:10101/index/repository/input/stargazer -d @json_input.json 
-```
-
-As defined in the input definition, field name `language_id` maps language to a corresponding id defined in `valueMap` and sets the appropriate bit in the `language` frame.  The value corresponding to field name `stargazer_id` is added to the `stargazer` frame as rowID.
-The data input above is equivalent to the following `SetBit()` operations:
-
-```
-curl localhost:10101/index/repository/query \
-     -X POST \
-     -d 'SetBit(frame="stargazer", columnID=91720568, rowID=513114)
-         SetBit(frame="stargazer", columnID=91720568, rowID=513114, timestamp="2017-05-18T20:40")
-         SetBit(frame="language", columnID=91720568, rowID=5)
-         SetBit(frame="language", columnID=95122322, rowID=17)
-     '
-```
+<div class="warning">
+Input definition is deprecated as of Pilosa v0.9.<br/>
+<br/>
+The previous version of this page is still available <a href="https://www.pilosa.com/docs/v0.8/input-definition">here</a>.
+</div>