Fix page headers

eric-schneider · eric-schneider · commit 5c82e3e2e2d5 · 2024-07-22T15:30:23.000-07:00
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarColumnWritetimeTimestamp.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarColumnWritetimeTimestamp.adoc
@@ -1,5 +1,4 @@
-= Specify writetime timestamp column 
-
+= Specify writetime timestamp column
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Apache Pulsar(TM) topic mapping, you can optionally specify which column should be used to note the timestamp when the Pulsar-produced record was inserted into any of the xref:index.adoc#supported-databases[supported databases].
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarConfigTasksMax.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarConfigTasksMax.adoc
@@ -1,5 +1,4 @@
-= Configuring parallelism 
-
+= Configuring parallelism
 :page-tag: pulsar-connector,admin,manage,pulsar
 
 For information on configuring parallelism for the DataStax Apache Pulsar(TM) Connector, see xref:opsPulsarScaling.adoc[].
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarConfigureErrorHandling.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarConfigureErrorHandling.adoc
@@ -1,5 +1,4 @@
-= Configure error handling 
-
+= Configure error handling
 :page-tag: pulsar-connector,admin,manage,pulsar
 
 The DataStax Apache Pulsar(TM) Connector provides an optional parameter, `ignoreErrors`.
@@ -13,9 +12,9 @@ ignoreErrors:: Use `ignoreErrors` settings to ignore specific types or all runti
 
 |`false`|No errors are ignored|Deprecated - equivalent to `NONE`
 |`true`|Only driver errors are ignored|Deprecated - equivalent to `DRIVER`
-|`NONE`|No errors are ignored; default behavior| 
-|`ALL`|All errors are ignored| 
-|`DRIVER`|Only driver errors are ignored| 
+|`NONE`|No errors are ignored; default behavior|
+|`ALL`|All errors are ignored|
+|`DRIVER`|Only driver errors are ignored|
 |===
 +
 If you set `ignoreErrors` to any value other than `false`, any erroneous record is logged once and the next record is picked up by the Pulsar Connector automatically.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarCqlQuery.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarCqlQuery.adoc
@@ -1,5 +1,4 @@
-= Provide CQL queries in mappings 
-
+= Provide CQL queries in mappings
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Pulsar topic mapping, you can optionally provide a CQL query that should run when the new record arrives on the Pulsar topic.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarDisplayingTopic.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarDisplayingTopic.adoc
@@ -1,5 +1,4 @@
 = Determining topic data structure
-
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 You can use the Apache Pulsar(TM) `pulsar-client` command line client to examine the structure of Pulsar messages for a topic.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarJsonMessageSchema.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarJsonMessageSchema.adoc
@@ -1,5 +1,4 @@
-= Mapping JSON messages 
-
+= Mapping JSON messages
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 The DataStax Apache Pulsar(TM) Connector supports mapping JSON messages with or without a schema.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc
@@ -1,5 +1,4 @@
-= Mapping Avro messages 
-
+= Mapping Avro messages
 :page-tag: pulsar-connector,dev,develop,pulsar,avro
 
 The DataStax Apache Pulsar(TM) Connector supports mapping individual fields from https://avro.apache.org/docs/1.8.1/gettingstartedjava.html[Avro] formatted key or values.
@@ -18,11 +17,11 @@ The Pulsar topic name is `users_topic` and have the following records:
 “favorite_color”: “pink”}`
 |user2|
 `{"`name`": "`shereen`", + "`favorite_number`":7, + "`favorite_color`": "`black`"}`
-|user3| 
+|user3|
 `{“name”: “kimberly”,
 “favorite_number”:11,
 “favorite_color”: “orange”}`
-|user4| 
+|user4|
 `{"`name`": "`taryn`", + "`favorite_number`":37, + "`favorite_color`": "`green`"}`
 
 The value field uses the following Avro Schema:
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapJson.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapJson.adoc
@@ -1,5 +1,4 @@
-= Mapping a message that contain JSON fields 
-
+= Mapping a message that contain JSON fields
 :page-tag: pulsar-connector,dev,develop,pulsar,json
 
 When the data format for the key or value is JSON, the DataStax Apache Pulsar(TM) Connector mapping can include individual fields in the JSON structure.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapKeyPair.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapKeyPair.adoc
@@ -1,5 +1,4 @@
-= Mapping basic messages to table columns 
-
+= Mapping basic messages to table columns
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 When messages are created using a Basic or primitive serializer, the message contains a key-value pair. Map the key and value to table columns. Ensure that the data types of the message field are compatible with the data type of the target column.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc
@@ -1,5 +1,4 @@
-= Mapping a topic to multiple tables 
-
+= Mapping a topic to multiple tables
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 The DataStax Apache Pulsar(TM) Connector allows for mapping a single topic to multiple tables for a single connector instance.
@@ -37,7 +36,7 @@ GENERAL MOTORS
 ----
 |
 AT&T
-| 
+|
 [source,no-highlight]
 ----
 {"symbol":"AT&T",
@@ -51,7 +50,7 @@ FORD MOTOR
 |
 [source,no-highlight]
 ----
-{"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"} 
+{"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 |===
 
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapTopicTable.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapTopicTable.adoc
@@ -1,5 +1,4 @@
-= Mapping pulsar topics to database tables 
-
+= Mapping pulsar topics to database tables
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 DataStax Apache Pulsar(TM) Connector has a simple yet powerful syntax for mapping fields from a Pulsar record to columns in a xref:index.adoc#supported-databases[supported database] table. An instance of the DataStax Apache Pulsar(TM) Connector can capture multiple topics and supports mapping a single topic to one or more tables.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapUdt.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapUdt.adoc
@@ -1,5 +1,4 @@
 = Mapping messages to table that has a User Defined Type
-
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 The DataStax Apache Pulsar(TM) Connector processes JSON, Avro, and complex types directly into a https://docs.datastax.com/en/dse/6.8/cql/cql/cql_using/useAlterType.html[user-defined type] column in the xref:index.adoc#supported-databases[supported database]. The Pulsar message embedded field names and the UDT field names must match.
@@ -84,7 +83,7 @@ topic:
 
 == Mapping complex user defined types
 
-The DataStax Apache Pulsar(TM) Connector supports mapping complex user defined types of `map`, `set`, and `list`. 
+The DataStax Apache Pulsar(TM) Connector supports mapping complex user defined types of `map`, `set`, and `list`.
 
 The DataStax keyspace name is `stocks_keyspace`. In the stocks keyspace create the user defined type, `stocks_complex_type`:
 
@@ -96,13 +95,13 @@ CREATE TYPE stocks_keyspace.stocks_complex_type (
     exchange text,
     industry text,
     value double,
-    trailing_five_days_value frozen<list<double>>, 
-    similar_symbols frozen<set<text>>, 
+    trailing_five_days_value frozen<list<double>>,
+    similar_symbols frozen<set<text>>,
     stats frozen<map<text, double>>);
 ----
 
 * `trailing_five_days_value frozen<list<double>>` contains a `list` of the value of the stock in the last five days, for example `[10.0, 11.0, 12.0, 23.0, 10.0]`. Values in a list do not need to be unique.
-* `similar_symbols frozen<set<text>>` contains a `set` of symbols in the same industry, or performing similarly, for example `["M", "GM", "F"]`. Values in a set must be unique. 
+* `similar_symbols frozen<set<text>>` contains a `set` of symbols in the same industry, or performing similarly, for example `["M", "GM", "F"]`. Values in a set must be unique.
 * `stats frozen<map<text, double>>` contains a `map` of key-value pairs, for example `{"open": 11.0, "high": 20.0, "low": 9.0}`.
 
 Define a table named `stocks_complex_udt_table` that has a column for the primitive string field `name` and a second column that uses the type, `stocks_complex_type`:
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMultTopicToTables.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMultTopicToTables.adoc
@@ -1,5 +1,4 @@
-= Multiple topics to multiple tables 
-
+= Multiple topics to multiple tables
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 The DataStax Apache Pulsar(TM) Connector allows for mapping multiple topics to multiple tables in a single connector instance.
@@ -12,13 +11,13 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 |===
 |key|value
 
-|APPLE| 
+|APPLE|
 [source,no-highlight]
----- 
+----
 {"symbol":"APPL", "value":208, "exchange":"NASDAQ", "industry":"TECH", "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|EXXON MOBIL| 
+|EXXON MOBIL|
 [source,no-highlight]
 ----
 {"symbol":"M",
@@ -28,13 +27,13 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|GENERAL MOTORS| 
+|GENERAL MOTORS|
 [source,no-highlight]
----- 
+----
 {"symbol":"GM", "value":38, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|AT&T| 
+|AT&T|
 [source,no-highlight]
 ----
 {"symbol":"AT&T",
@@ -44,9 +43,9 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|FORD MOTOR| 
+|FORD MOTOR|
 [source,no-highlight]
----- 
+----
 {"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 |===
@@ -57,7 +56,7 @@ And `baseball_topic` has the same structure, basic key and JSON value.
 |===
 |key|value
 
-|redsox| 
+|redsox|
 [source,no-highlight]
 ----
 {"number":50,
@@ -67,13 +66,13 @@ And `baseball_topic` has the same structure, basic key and JSON value.
 "city":"boston"}
 ----
 
-|redsox| 
+|redsox|
 [source,no-highlight]
----- 
+----
 {"number":28, "firstname":"jd", "lastname":"martinez", "street":"4 yawkey way", "city":"boston"}
 ----
 
-|redsox| 
+|redsox|
 [source,no-highlight]
 ----
 {"number":16,
@@ -83,13 +82,13 @@ And `baseball_topic` has the same structure, basic key and JSON value.
 "city":"boston"}
 ----
 
-|redsox| 
+|redsox|
 [source,no-highlight]
----- 
+----
 {"number":41, "firstname":"chris", "lastname":"sale", "street":"4 yawkey way", "city":"boston"}
 ----
 
-|redsox| 
+|redsox|
 [source,no-highlight]
 ----
 {"number":24,
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarNowFunction.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarNowFunction.adoc
@@ -1,5 +1,4 @@
-= The now() function in mappings 
-
+= The now() function in mappings
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Apache Pulsar(TM) topic mapping, you can use the ``now()``function.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarRecordHeaderToTable.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarRecordHeaderToTable.adoc
@@ -1,5 +1,4 @@
-= Extract Pulsar record header values 
-
+= Extract Pulsar record header values
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Apache Pulsar(TM) topic mapping, you can extract values from the message properties, and write the values to a xref:index.adoc#supported-databases[supported database table].
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSelectiveUpdateMapsAndUdts.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSelectiveUpdateMapsAndUdts.adoc
@@ -1,5 +1,4 @@
-= Selectively update maps and UDTs based on Pulsar fields 
-
+= Selectively update maps and UDTs based on Pulsar fields
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Apache Pulsar(TM) topic mapping, you can selectively update maps and User Defined Types (UDTs) based on whether Pulsar fields have present values. That is, any value other than `null`.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSettingJavaDriverConfig.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSettingJavaDriverConfig.adoc
@@ -1,5 +1,4 @@
-= Pass Pulsar Connector settings directly to the DataStax Java driver 
-
+= Pass Pulsar Connector settings directly to the DataStax Java driver
 :page-tag: pulsar-connector,dev,develop,pulsar,java
 
 In your DataStax Apache Pulsar(TM) Connector configuration file, you can directly pass settings to the DataStax Java driver by using the `datastax-java-driver` prefix.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSettingRowLevelTtl.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarSettingRowLevelTtl.adoc
@@ -1,5 +1,4 @@
-= Setting row-level TTL values from Pulsar fields 
-
+= Setting row-level TTL values from Pulsar fields
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 In the Apache Pulsar(TM) topic mapping, you can optionally specify which column should be used as the ttl (time-to-live) of the record being inserted into the database table.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarStringJson.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarStringJson.adoc
@@ -1,5 +1,4 @@
-= Mapping a message that contains both basic and JSON fields 
-
+= Mapping a message that contains both basic and JSON fields
 :page-tag: pulsar-connector,dev,develop,pulsar,json
 
 When the data format for the message key or value is JSON, the DataStax Apache Pulsar(TM) connector mapping can include individual fields in the JSON structure.
@@ -11,13 +10,13 @@ The key is mapped to the name field and each of the JSON fields to a separate co
 |===
 |key|value
 
-|APPLE| 
+|APPLE|
 [source,no-highlight]
 ----
 {"symbol":"APPL", "value":208, "exchange":"NASDAQ", "industry":"TECH", "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|EXXON MOBIL| 
+|EXXON MOBIL|
 [source,no-highlight]
 ----
 {"symbol":"M",
@@ -27,13 +26,13 @@ The key is mapped to the name field and each of the JSON fields to a separate co
 "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|GENERAL MOTORS| 
+|GENERAL MOTORS|
 [source,no-highlight]
----- 
+----
 {"symbol":"GM", "value":38, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|AT&T| 
+|AT&T|
 [source,no-highlight]
 ----
 {"symbol":"AT&T",
@@ -43,9 +42,9 @@ The key is mapped to the name field and each of the JSON fields to a separate co
 "ts":"2018-11-26T19:26:27.483"}
 ----
 
-|FORD MOTOR| 
+|FORD MOTOR|
 [source,no-highlight]
----- 
+----
 {"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"} `
 ----
 |===
@@ -103,7 +102,7 @@ nodetool describering -- keyspace\_name
 Example configurations for `stocks_topic` to `stocks_table` using the minimum required settings:
 +
 [source,language-yaml]
----- 
+----
 tasks.max: 1
 topics: stocks_topic
 topic
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarAuthLdap.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarAuthLdap.adoc
@@ -1,5 +1,4 @@
 = Internal or LDAP authentication
-
 :page-tag: pulsar-connector,security,secure,pulsar
 
 When the cluster has internal or LDAP authentication enabled, configure the user name and password settings for DataStax Apache Pulsar(TM) Connector.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDates.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDates.adoc
@@ -1,5 +1,4 @@
-= Converting date and times for a topic 
-
+= Converting date and times for a topic
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 Use the following syntax to configure date and time conversion parameters for each Pulsar topic.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDseConnection.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDseConnection.adoc
@@ -1,5 +1,4 @@
-= DataStax connection 
-
+= DataStax connection
 :page-tag: pulsar-connector,admin,dev,connect,pulsar
 
 Configure the connection settings from Apache Pulsar(TM) to the cluster.
@@ -9,13 +8,13 @@ Configure the connection settings from Apache Pulsar(TM) to the cluster.
 [source,language-yaml]
 ----
  connectionPoolLocalSize: 4
- contactPoints: [dse_host_list] 
- loadBalancing.localDc: datacenter_name 
- port: 9042 
- maxConcurrentRequests: 500 
- maxNumberOfRecordsInBatch: 32 
- queryExecutionTimeout: 30 
- jmx: true 
+ contactPoints: [dse_host_list]
+ loadBalancing.localDc: datacenter_name
+ port: 9042
+ maxConcurrentRequests: 500
+ maxNumberOfRecordsInBatch: 32
+ queryExecutionTimeout: 30
+ jmx: true
  compression: None
 ----
 
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDseTable.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarDseTable.adoc
@@ -1,5 +1,4 @@
-= Pulsar topic-to-table settings 
-
+= Pulsar topic-to-table settings
 :page-tag: pulsar-connector,dev,develop,pulsar
 
 Capture Apache Pulsar(TM) topics in the xref:index.adoc#supported-databases[supported database] by specifying a target keyspace, table, and then map the topic fields to table columns in the name of the parameter.
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarSsl.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/cfgRefPulsarSsl.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/index.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/index.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarAddField.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarAddField.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarAddTableColumn.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarAddTableColumn.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarChangeSchema.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarChangeSchema.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarRemoveColumn.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarRemoveColumn.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarRemoveField.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/opsPulsarRemoveField.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsLargeBatches.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsLargeBatches.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsLoadBalancing.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsLoadBalancing.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsRecordFailsToWriteToTable.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsRecordFailsToWriteToTable.adoc
diff --git a/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsRecordParsingFails.adoc b/docs-src/pulsar-sink-core/modules/ROOT/pages/trbPulsarTsRecordParsingFails.adoc

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,4 @@`
`1`	`1`	`= Determining topic data structure`
`2`		`-`
`3`	`2`	`:page-tag: pulsar-connector,dev,develop,pulsar`
`4`	`3`
`5`	`4`	You can use the Apache Pulsar(TM) `pulsar-client` command line client to examine the structure of Pulsar messages for a topic.