Convert more connector docs to markdown

- All JBDC based connectors
- Kafka and related connectors with some layout improvements
- Blackhole connector
- All used fragments

docs/src/main/sphinx/conf.py

@@ -115,7 +115,8 @@ def setup(app):
 
 myst_enable_extensions = [
     "colon_fence",
-    "deflist"
+    "deflist",
+    "substitution"
 ]
 
 # -- Options for HTML output ---------------------------------------------------

docs/src/main/sphinx/connector/alter-schema-limitation.fragment

@@ -1,5 +1,4 @@
-ALTER SCHEMA
-^^^^^^^^^^^^
+### ALTER SCHEMA
 
-The connector supports renaming a schema with the ``ALTER SCHEMA RENAME``
-statement. ``ALTER SCHEMA SET AUTHORIZATION`` is not supported.
+The connector supports renaming a schema with the `ALTER SCHEMA RENAME`
+statement. `ALTER SCHEMA SET AUTHORIZATION` is not supported.

docs/src/main/sphinx/connector/alter-table-limitation.fragment

@@ -1,16 +1,15 @@
-ALTER TABLE RENAME TO
-^^^^^^^^^^^^^^^^^^^^^
+### ALTER TABLE RENAME TO
 
 The connector does not support renaming tables across multiple schemas. For
 example, the following statement is supported:
 
-.. code-block:: sql
-
-    ALTER TABLE example.schema_one.table_one RENAME TO example.schema_one.table_two
+```sql
+ALTER TABLE example.schema_one.table_one RENAME TO example.schema_one.table_two
+```
 
 The following statement attempts to rename a table across schemas, and therefore
 is not supported:
 
-.. code-block:: sql
-
-    ALTER TABLE example.schema_one.table_one RENAME TO example.schema_two.table_two
+```sql
+ALTER TABLE example.schema_one.table_one RENAME TO example.schema_two.table_two
+```

docs/src/main/sphinx/connector/avro-decoder.fragment

@@ -1,28 +1,28 @@
-Avro decoder
-""""""""""""
+#### Avro decoder
 
 The Avro decoder converts the bytes representing a message or key in Avro format
 based on a schema. The message must have the Avro schema embedded. Trino does
 not support schemaless Avro decoding.
 
-The ``dataSchema`` must be defined for any key or message using ``Avro``
-decoder. ``Avro`` decoder should point to the location of a valid Avro
+The `dataSchema` must be defined for any key or message using `Avro`
+decoder. `Avro` decoder should point to the location of a valid Avro
 schema file of the message which must be decoded. This location can be a remote
-web server (e.g.: ``dataSchema: 'http://example.org/schema/avro_data.avsc'``) or
-local file system(e.g.: ``dataSchema: '/usr/local/schema/avro_data.avsc'``). The
+web server (e.g.: `dataSchema: 'http://example.org/schema/avro_data.avsc'`) or
+local file system(e.g.: `dataSchema: '/usr/local/schema/avro_data.avsc'`). The
 decoder fails if this location is not accessible from the Trino cluster.
 
 The following attributes are supported:
 
-* ``name`` - Name of the column in the Trino table.
-* ``type`` - Trino data type of column.
-* ``mapping`` - A slash-separated list of field names to select a field from the
-  Avro schema. If the field specified in ``mapping`` does not exist in the
-  original Avro schema, a read operation returns ``NULL``.
+- `name` - Name of the column in the Trino table.
+- `type` - Trino data type of column.
+- `mapping` - A slash-separated list of field names to select a field from the
+  Avro schema. If the field specified in `mapping` does not exist in the
+  original Avro schema, a read operation returns `NULL`.
 
-The following table lists the supported Trino types that can be used in ``type``
+The following table lists the supported Trino types that can be used in `type`
 for the equivalent Avro field types:
 
+```{eval-rst}
 .. list-table::
   :widths: 40, 60
   :header-rows: 1
@@ -43,11 +43,11 @@ for the equivalent Avro field types:
     - ``ARRAY``
   * - ``MAP``
     - ``MAP``
+```
 
 No other types are supported.
 
-Avro schema evolution
-+++++++++++++++++++++
+##### Avro schema evolution
 
 The Avro decoder supports schema evolution with backward compatibility. With
 backward compatibility, a newer schema can be used to read Avro data created
@@ -57,16 +57,13 @@ default value in the Avro schema file.
 
 The schema evolution behavior is as follows:
 
-* Column added in new schema: Data created with an older schema produces a
+- Column added in new schema: Data created with an older schema produces a
   *default* value when the table is using the new schema.
-
-* Column removed in new schema: Data created with an older schema no longer
+- Column removed in new schema: Data created with an older schema no longer
   outputs the data from the column that was removed.
-
-* Column is renamed in the new schema: This is equivalent to removing the column
+- Column is renamed in the new schema: This is equivalent to removing the column
   and adding a new one, and data created with an older schema produces a
   *default* value when the table is using the new schema.
-
-* Changing type of column in the new schema: If the type coercion is supported
+- Changing type of column in the new schema: If the type coercion is supported
   by Avro, then the conversion happens. An error is thrown for incompatible
   types.