hotfix: fix line protocol code blocks, #closes influxdata/DAR#423

content/enterprise_influxdb/v1/write_protocols/line_protocol_reference.md

@@ -23,7 +23,9 @@ InfluxDB line protocol is a text-based format for writing points to InfluxDB.
 
 Line protocol accepts the newline character `\n` and is whitespace-sensitive.
 
->**Note** Line protocol does not support the newline character `\n` in tag values or field values.
+{{% note %}}
+Line protocol does not support the newline character `\n` in tag values or field values.
+{{% /note %}}
 
 ### Syntax description
 
@@ -36,12 +38,14 @@ InfluxDB line protocol informs InfluxDB of the data's measurement, tag set, fiel
 | [Field set](/enterprise_influxdb/v1/concepts/glossary/#field-set) | Required. Points must have at least one field. | All field key-value pairs for the point. | [Field keys](/enterprise_influxdb/v1/concepts/glossary/#field-key) are strings. [Field values](/enterprise_influxdb/v1/concepts/glossary/#field-value) can be floats, integers, strings, or Booleans.
 | [Timestamp](/enterprise_influxdb/v1/concepts/glossary/#timestamp) | Optional. InfluxDB uses the server's local nanosecond timestamp in UTC if the timestamp is not included with the point. | The timestamp for the data point. InfluxDB accepts one timestamp per point. | Unix nanosecond timestamp. Specify alternative precisions with the [InfluxDB API](/enterprise_influxdb/v1/tools/api/#write-http-endpoint).
 
-> #### Performance tips:
+{{% note %}}
->
+#### Performance tips:
+
 - Before sending data to InfluxDB, sort by tag key to match the results from the
 [Go bytes.Compare function](http://golang.org/pkg/bytes/#Compare).
 - To significantly improve compression, use the coarsest [precision](/enterprise_influxdb/v1/tools/api/#write-http-endpoint) possible for timestamps.
 - Use the Network Time Protocol (NTP) to synchronize time between hosts. InfluxDB uses a host's local time in UTC to assign timestamps to data. If a host's clock isn't synchronized with NTP, the data that the host writes to InfluxDB may have inaccurate timestamps.
+{{% /note %}}
 
 ## Data types
 
@@ -139,12 +143,12 @@ If the timestamps on the float and string are not stored in the same shard:
 ### Quoting
 
 | Element                                        | Double quotes                                                                        | Single quotes          |
-| :------ | :------------ |:------------- |
+| :--------------------------------------------- | :----------------------------------------------------------------------------------- | :--------------------- |
 | Timestamp                                      | Never                                                                                | Never                  |
-| Measurements, tag keys, tag values, field keys | Never* | Never* |
+| Measurements, tag keys, tag values, field keys | Never{{% req "\\*" %}}                                                               | Never{{% req "\\*" %}} |
 | Field values                                   | Double quote string field values. Do not double quote floats, integers, or Booleans. | Never                  |
 
-\* InfluxDB line protocol allows users to double and single quote measurement names, tag
+{{% req "\\*" %}} InfluxDB line protocol allows users to double and single quote measurement names, tag
 keys, tag values, and field keys.
 It will, however, assume that the double or single quotes are part of the name,
 key, or value.
@@ -201,29 +205,25 @@ measurement require both double quotes and escaped (`\`) double quotes in the
 
 You must use a backslash character `\` to escape the following special characters:
 
-* In string field values, you must escape:
+- In string field values, you must escape:
-  * double quotes  
+  - double quotes: `\"` escapes double quote.
-  * backslash character
+  - backslash character: If you use multiple backslashes, they must be escaped.
+    InfluxDB interprets backslashes as follows:
   
-For example, `\"` escapes double quote.
+    - `\` or `\\` interpreted as `\`
+    - `\\\` or `\\\\` interpreted as `\\`
+    - `\\\\\` or `\\\\\\` interpreted as `\\\`, and so on
 
->#### Note on backslashes:
+- In tag keys, tag values, and field keys, you must escape:
->
+  - commas
-* If you use multiple backslashes, they must be escaped. Influx interprets backslashes as follows:
+  - equal signs
-  *	`\` or `\\` interpreted as `\`
+  - spaces
-  *	`\\\` or `\\\\` interpreted as `\\`
-  * `\\\\\` or `\\\\\\` interpreted as `\\\`, and so on
-
-* In tag keys, tag values, and field keys, you must escape:
-  * commas
-  * equal signs
-  * spaces
 
 For example, `\,` escapes a comma.
 
-* In measurements, you must escape:
+- In measurements, you must escape:
-  * commas  
+  - commas  
-  * spaces
+  - spaces
 
 You do not need to escape other special characters.
 

content/enterprise_influxdb/v1/write_protocols/line_protocol_tutorial.md

@@ -18,14 +18,11 @@ write points (unless you're using a [service plugin](/enterprise_influxdb/v1/sup
 Using fictional temperature data, this page introduces InfluxDB line protocol.
 It covers:
 
-<table style="width:100%">
+- [Syntax](#syntax)
-  <tr>
+- [Data types](#data-types)
-    <td><a href="#syntax">Syntax</a></td>
+- [Quoting](#quoting)
-    <td><a href="#data-types">Data Types</a></td>
+- [Special characters and keywords](#special-characters-and-keywords)
-    <td><a href="#quoting">Quoting</a></td>
+- [Writing data to InfluxDB](#writing-data-to-influxdb)
-    <td><a href="#special-characters-and-keywords">Special Characters and Keywords</a></td>
-  </tr>
-</table>
 
 The final section, [Writing data to InfluxDB](#writing-data-to-influxdb),
 describes how to get data into InfluxDB and how InfluxDB handles Line
@@ -36,18 +33,8 @@ Protocol duplicates.
 A single line of text in line protocol format represents one data point in InfluxDB.
 It informs InfluxDB of the point's measurement, tag set, field set, and
 timestamp.
-The following code block shows a sample of line protocol and breaks it into its
-individual components:
 
-```
+{{< influxdb/line-protocol >}}
-weather,location=us-midwest temperature=82 1465839830100400200
-  |    -------------------- --------------  |
-  |             |             |             |
-  |             |             |             |
-+-----------+--------+-+---------+-+---------+
-|measurement|,tag_set| |field_set| |timestamp|
-+-----------+--------+-+---------+-+---------+
-```
 
 Moving across each element in the diagram:
 
@@ -65,7 +52,10 @@ The [tag(s)](/enterprise_influxdb/v1/concepts/glossary/#tag) that you want to in
 with your data point.
 Tags are optional in line protocol.
 
-> **Note:** Avoid using the reserved keys `_field`, `_measurement`, and `time`. If reserved keys are included as a tag or field key, the associated point is discarded.
+{{% note %}}
+Avoid using the reserved keys `_field`, `_measurement`, and `time`.
+If reserved keys are included as a tag or field key, the associated point is discarded.
+{{% /note %}}
 
 Notice that the measurement and tag set are separated by a comma and no spaces.
 
@@ -93,7 +83,7 @@ database.
 The sort should match the results from the
 [Go bytes.Compare function](http://golang.org/pkg/bytes/#Compare).
 
-### Whitespace I
+### First whitespace
 
 Separate the measurement and the field set or, if you're including a tag set
 with your data point, separate the tag set and the field set with a whitespace.
@@ -129,7 +119,7 @@ Adding another field (`humidity=71`) to the example looks like this:
 weather,location=us-midwest temperature=82,humidity=71 1465839830100400200
 ```
 
-### Whitespace II
+### Second whitespace
 
 Separate the field set and the optional timestamp with a whitespace.
 The whitespace is required in line protocol if you're including a timestamp.
@@ -158,12 +148,14 @@ We recommend using the coarsest precision possible as this can result in
 significant improvements in compression.
 See the [API Reference](/enterprise_influxdb/v1/tools/api/#write-http-endpoint) for more information.
 
-> #### Setup Tip:
+{{% note %}}
->
+#### Use NTP to synchronize time between hosts
+
 Use the Network Time Protocol (NTP) to synchronize time between hosts.
 InfluxDB uses a host's local time in UTC to assign timestamps to data; if
 hosts' clocks aren't synchronized with NTP, the timestamps on the data written
 to InfluxDB can be inaccurate.
+{{% /note %}}
 
 ## Data types
 
@@ -178,15 +170,16 @@ This section covers the data types of line protocol's major components:
 
 Measurements, tag keys, tag values, and field keys are always strings.
 
-> **Note:**
+{{% note %}}
 Because InfluxDB stores tag values as strings, InfluxDB cannot perform math on
 tag values.
 In addition, InfluxQL [functions](/enterprise_influxdb/v1/query_language/functions/)
 do not accept a tag value as a primary argument.
 It's a good idea to take into account that information when designing your
 [schema](/enterprise_influxdb/v1/concepts/glossary/#schema).
+{{% /note %}}
 
-Timestamps are UNIX timestamps.
+Timestamps are Unix timestamps.
 The minimum valid timestamp is `-9223372036854775806` or `1677-09-21T00:12:43.145224194Z`.
 The maximum valid timestamp is `9223372036854775806` or `2262-04-11T23:47:16.854775806Z`.
 As mentioned above, by default, InfluxDB assumes that timestamps have
@@ -196,7 +189,7 @@ alternative precisions.
 
 Field values can be floats, integers, strings, or Booleans:
 
-* Floats - by default, InfluxDB assumes all numerical field values are floats.
+- **Floats**: by default, InfluxDB assumes all numeric field values are floats.
 
   Store the field value `82` as a float:
 
@@ -204,7 +197,7 @@ Field values can be floats, integers, strings, or Booleans:
   weather,location=us-midwest temperature=82 1465839830100400200
   ```
 
-* Integers - append an `i` to the field value to tell InfluxDB to store the
+- **Integers**: append an `i` to the field value to tell InfluxDB to store the
   number as an integer.
 
   Store the field value `82` as an integer:
@@ -213,8 +206,8 @@ number as an integer.
   weather,location=us-midwest temperature=82i 1465839830100400200
   ```
 
-* Strings - double quote string field values (more on quoting in line protocol
+- **Strings**: double quote string field values (more on quoting in line
-[below](#quoting)).
+  protocol [below](#quoting)).
 
   Store the field value `too warm` as a string:
 
@@ -222,7 +215,7 @@ weather,location=us-midwest temperature=82i 1465839830100400200
   weather,location=us-midwest temperature="too warm" 1465839830100400200
   ```
 
-* Booleans - specify TRUE with `t`, `T`, `true`, `True`, or `TRUE`. Specify
+- **Booleans**: specify TRUE with `t`, `T`, `true`, `True`, or `TRUE`. Specify
 FALSE with `f`, `F`, `false`, `False`, or `FALSE`.
 
   Store the field value `true` as a Boolean:
@@ -231,10 +224,11 @@ FALSE with `f`, `F`, `false`, `False`, or `FALSE`.
   weather,location=us-midwest too_hot=true 1465839830100400200
   ```
 
-    > **Note:** Acceptable Boolean syntax differs for data writes and data
+  {{% note %}}
-    queries. See
+  Acceptable Boolean syntax differs for data writes and data
-    [Frequently Asked Questions](/enterprise_influxdb/v1/troubleshooting/frequently-asked-questions/#why-can-t-i-query-boolean-field-values)
+  queries. See [Frequently Asked Questions](/enterprise_influxdb/v1/troubleshooting/frequently-asked-questions/#why-can-t-i-query-boolean-field-values)
   for more information.
+  {{% /note %}}
 
 Within a measurement, a field's type cannot differ within a
 [shard](/enterprise_influxdb/v1/concepts/glossary/#shard), but it can differ across
@@ -267,36 +261,29 @@ This section covers when not to and when to double (`"`) or single (`'`)
 quote in line protocol.
 Moving from never quote to please do quote:
 
-* Never double or single quote the timestamp.
+- Never double or single quote the timestamp--for example:
-It's not valid line protocol.
 
-    Example:
+  ```sql
-
-    ```
   > INSERT weather,location=us-midwest temperature=82 "1465839830100400200"
   ERR: {"error":"unable to parse 'weather,location=us-midwest temperature=82 \"1465839830100400200\"': bad timestamp"}
   ```
 
-* Never single quote field values (even if they're strings!).
+- Never single quote field values, even if they're strings--for example:
-It's also not valid line protocol.
 
-    Example:
+  ```sql
-
-    ```
   > INSERT weather,location=us-midwest temperature='too warm'
   ERR: {"error":"unable to parse 'weather,location=us-midwest temperature='too warm'': invalid boolean"}
   ``` 
 
-* Do not double or single quote measurement names, tag keys, tag values, and field
+- Do not double or single quote measurement names, tag keys, tag values, and field
-keys.
+  keys unless the quotes are part of the name--for example:
-It is valid line protocol but InfluxDB assumes that the quotes are part of the
-name.
 
-    Example:
+  ```sql
-
-    ```
   > INSERT weather,location=us-midwest temperature=82 1465839830100400200
   > INSERT "weather",location=us-midwest temperature=87 1465839830100400200
+  ```
+  
+  ```
   > SHOW MEASUREMENTS
   name: measurements
   ------------------
@@ -308,30 +295,27 @@ weather
   To query data in `"weather"` you need to double quote the measurement name and
   escape the measurement's double quotes:
 
-    ```
+  ```sql
   > SELECT * FROM "\"weather\""
+    
   name: "weather"
   ---------------
   time				            location	 temperature
   2016-06-13T17:43:50.1004002Z	us-midwest	 87
   ```
 
-* Do not double quote field values that are floats, integers, or Booleans.
+- Do not double quote field values that are floats, integers, or Booleans.
-InfluxDB will assume that those values are strings.
+  InfluxDB parses quoted field values as strings--for example:
 
-    Example:
+  ```sql
-
-    ```
   > INSERT weather,location=us-midwest temperature="82"
   > SELECT * FROM weather WHERE temperature >= 70
   >
   ```
 
-* Do double quote field values that are strings.
+- Do double quote field values that are strings--for example:
 
-    Example:
+  ```sql
-
-    ```
   > INSERT weather,location=us-midwest temperature="too warm"
   > SELECT * FROM weather
   name: weather
@@ -347,17 +331,17 @@ time				            location	 temperature
 For tag keys, tag values, and field keys always use a backslash character `\`
 to escape:
 
-* commas `,`
+- commas (`,`)
 
   ```
   weather,location=us\,midwest temperature=82 1465839830100400200
   ```
-* equal signs `=`
+- equal signs (`=`)
 
   ```
   weather,location=us-midwest temp\=rature=82 1465839830100400200
   ```
-* spaces
+- spaces
 
   ```
   weather,location\ place=us-midwest temperature=82 1465839830100400200
@@ -365,13 +349,13 @@ weather,location\ place=us-midwest temperature=82 1465839830100400200
 
 For measurements always use a backslash character `\` to escape:
 
-* commas `,`
+- commas (`,`)
 
   ```
   wea\,ther,location=us-midwest temperature=82 1465839830100400200
   ```
 
-* spaces
+- spaces
 
   ```
   wea\ ther,location=us-midwest temperature=82 1465839830100400200
@@ -379,14 +363,14 @@ wea\ ther,location=us-midwest temperature=82 1465839830100400200
 
 For string field values use a backslash character `\` to escape:
 
-* double quotes `"`
+- double quotes (`"`)
 
   ```
   weather,location=us-midwest temperature="too\"hot\"" 1465839830100400200
   ```
 
-line protocol does not require users to escape the backslash character `\` but
+Line protocol does not require you to escape the backslash character `\` but
-will not complain if you do. For example, inserting the following:
+you can if you want to--for example:
 
 ```
 weather,location=us-midwest temperature_str="too hot/cold" 1465839830100400201
@@ -397,11 +381,9 @@ weather,location=us-midwest temperature_str="too hot\\\\cold" 146583983010040020
 weather,location=us-midwest temperature_str="too hot\\\\\cold" 1465839830100400206
 ```
 
-Will be interpreted as follows (notice that a single and double backslash produce the same record):
+Is interpreted as:
 
 ```sql
-> SELECT * FROM "weather"
-name: weather
 time                location   temperature_str
 ----                --------   ---------------
 1465839830100400201 us-midwest too hot/cold
@@ -412,6 +394,10 @@ time                location   temperature_str
 1465839830100400206 us-midwest too hot\\\cold
 ```
 
+{{% note %}}
+Notice that a single and double backslash produce the same record.
+{{% /note %}}
+
 All other special characters also do not require escaping.
 For example, line protocol handles emojis with no problem: