Fix docs and a test

docs/en/engines/table-engines/integrations/time-series.md

@@ -8,7 +8,7 @@ sidebar_label: TimeSeries
 
 A table engine storing time series, i.e. a set of values associated with timestamps and tags (or labels):
 
-```
+```text
 metric_name1[tag1=value1, tag2=value2, ...] = {timestamp1: value1, timestamp2: value2, ...}
 metric_name2[...] = ...
 ```
@@ -39,6 +39,7 @@ CREATE TABLE my_table ENGINE=TimeSeries
 ```
 
 Then this table can be used with the following protocols (a port must be assigned in the server configuration):
+
 - [prometheus remote-write](../../../interfaces/prometheus.md#remote-write)
 - [prometheus remote-read](../../../interfaces/prometheus.md#remote-read)
 
@@ -53,6 +54,7 @@ The target tables can be either specified explicitly in the `CREATE TABLE` query
 or the `TimeSeries` table engine can generate inner target tables automatically.
 
 The target tables are the following:
+
 1. The _data_ table {#data-table} contains time series associated with some identifier.
 The _data_ table must have columns:
 
@@ -71,7 +73,7 @@ The _tags_ table must have columns:
 | `metric_name` | [x] | `LowCardinality(String)` | `String` or `LowCardinality(String)` | The name of a metric |
 | `<tag_value_column>` | [ ] | `String` | `String` or `LowCardinality(String)` or `LowCardinality(Nullable(String))` | The value of a specific tag, the tag's name and the name of a corresponding column are specified in the [tags_to_columns](#settings) setting |
 | `tags` | [x] | `Map(LowCardinality(String), String)` | `Map(String, String)` or `Map(LowCardinality(String), String)` or `Map(LowCardinality(String), LowCardinality(String))` | Map of tags excluding the tag `__name__` containing the name of a metric and excluding tags with names enumerated in the [tags_to_columns](#settings) setting |
-| `all_tags` | [ ] | `Map(String, String)` | `Map(String, String)` or `Map(LowCardinality(String), String)` or `Map(LowCardinality(String), LowCardinality(String))` | Ephemeral column, each row is a map of all the tags excluding only the tag `__name__` containing the name of a metric. The only purpose of that column is to be used while calculating `id` |
+| `all_tags` | [ ] | `Map(String, LowCardinality(String))` | `Map(String, String)` or `Map(LowCardinality(String), String)` or `Map(LowCardinality(String), LowCardinality(String))` | Ephemeral column, each row is a map of all the tags excluding only the tag `__name__` containing the name of a metric. The only purpose of that column is to be used while calculating `id` |
 | `min_time` | [ ] | `Nullable(DateTime64(3))` | `DateTime64(X)` or `Nullable(DateTime64(X))` | Minimum timestamp of time series with that `id`. The column is created if [store_min_time_and_max_time](#settings) is `true` |
 | `max_time` | [ ] | `Nullable(DateTime64(3))` | `DateTime64(X)` or `Nullable(DateTime64(X))` | Maximum timestamp of time series with that `id`. The column is created if [store_min_time_and_max_time](#settings) is `true` |
 
@@ -239,6 +241,7 @@ ENGINE=TimeSeries SETTINGS = {'instance': 'instance', 'job': 'job'}
 ## Table engines of inner target tables {#inner-table-engines}
 
 By default inner target tables use the following table engines:
+
 - the [data]{#data-table} table uses [MergeTree](../mergetree-family/mergetree);
 - the [tags]{#tags-table} table uses [AggregatingMergeTree](../mergetree-family/aggregatingmergetree) because the same data is often inserted multiple times to this table so we need a way
 to remove duplicates, and also because it's required to do aggregation for columns `min_time` and `max_time`;
@@ -287,9 +290,10 @@ Here is a list of settings which can be specified while defining a `TimeSeries`
 | `aggregate_min_time_and_max_time` | Bool | true | When creating an inner target `tags` table, this flag enables using `SimpleAggregateFunction(min, Nullable(DateTime64(3)))` instead of just `Nullable(DateTime64(3))` as the type of the `min_time` column, and the same for the `max_time` column |
 | `filter_by_min_time_and_max_time` | Bool | true | If set to true then the table will use the `min_time` and `max_time` columns for filtering time series |
 
-# Functions {#functions}
+## Functions {#functions}
 
 Here is a list of functions supporting a `TimeSeries` table as an argument:
+
 - [timeSeriesData](../../../sql-reference/table-functions/timeSeriesData.md)
 - [timeSeriesTags](../../../sql-reference/table-functions/timeSeriesTags.md)
 - [timeSeriesMetrics](../../../sql-reference/table-functions/timeSeriesMetrics.md)

docs/en/interfaces/prometheus.md

@@ -58,6 +58,7 @@ Settings:
 | `errors` | true | Expose the number of errors by error codes occurred since the last server restart. This information could be obtained from the [system.errors](../operations/system-tables/errors.md) as well. |
 
 Check (replace `127.0.0.1` with the IP addr or hostname of your ClickHouse server):
+
 ```bash
 curl 127.0.0.1:9363/metrics
 ```

tests/integration/test_prometheus_protocols/test.py

@@ -144,6 +144,11 @@ def test_inner_engines():
 
 
 def test_external_tables():
+    node.query("DROP TABLE IF EXISTS mydata")
+    node.query("DROP TABLE IF EXISTS mytags")
+    node.query("DROP TABLE IF EXISTS mymetrics")
+    node.query("DROP TABLE IF EXISTS prometheus")
+
     node.query(
         "CREATE TABLE mydata (id UUID, timestamp DateTime64(3), value Float64) "
         "ENGINE=MergeTree ORDER BY (id, timestamp)"