Add tags

johnsmartco · johnsmartco · commit 8ae1f8a494ce · 2022-01-28T13:11:59.000-07:00
diff --git a/modules/ROOT/pages/cfgPulsarColumnWritetimeTimestamp.adoc b/modules/ROOT/pages/cfgPulsarColumnWritetimeTimestamp.adoc
@@ -1,5 +1,7 @@
 = Specify writetime timestamp column 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 In the Apache Pulsar™ 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].
 
 The mapping setting provides a special property, `__timestamp`.
diff --git a/modules/ROOT/pages/cfgPulsarConfigTasksMax.adoc b/modules/ROOT/pages/cfgPulsarConfigTasksMax.adoc
@@ -1,3 +1,5 @@
 = Configuring parallelism 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 For information on configuring parallelism for the DataStax Apache Pulsar™ Connector, see xref:opsPulsarScaling.adoc[].
diff --git a/modules/ROOT/pages/cfgPulsarConfigureErrorHandling.adoc b/modules/ROOT/pages/cfgPulsarConfigureErrorHandling.adoc
@@ -1,5 +1,7 @@
 = Configure error handling 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 The DataStax Apache Pulsar™ Connector provides an optional parameter, `ignoreErrors`.
 When set to `true`, it allows the connector to continue processing records even after an error occurred on the prior record.
 
diff --git a/modules/ROOT/pages/cfgPulsarCqlQuery.adoc b/modules/ROOT/pages/cfgPulsarCqlQuery.adoc
@@ -1,5 +1,7 @@
 = 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.
 
 NOTE: This feature is only meant for advanced use cases. Most often, you can use the standard Pulsar mapping without a query. If you define a query in the topic-to-table mapping, the query has priority and will be used instead of the automatically generated action.
diff --git a/modules/ROOT/pages/cfgPulsarDisplayingTopic.adoc b/modules/ROOT/pages/cfgPulsarDisplayingTopic.adoc
@@ -1,5 +1,7 @@
 = Determining topic data structure 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 You can use the Apache Pulsar™ `pulsar-client` command line client to examine the structure of Pulsar messages for a topic.
 
 link:https://pulsar.apache.org/docs/en/reference-cli-tools/#consume/[]
diff --git a/modules/ROOT/pages/cfgPulsarJsonMessageSchema.adoc b/modules/ROOT/pages/cfgPulsarJsonMessageSchema.adoc
@@ -1,5 +1,7 @@
 = Mapping JSON messages 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 The DataStax Apache Pulsar™ Connector supports mapping JSON messages with or without a schema.
 In this example, the key is regular JSON without schema.
 The value is also JSON but contains a schema and a payload.
diff --git a/modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc b/modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc
@@ -1,5 +1,7 @@
 = Mapping Avro messages 
 
+:page-tag: pulsar-connector,dev,develop,pulsar,avro
+
 The DataStax Apache Pulsar™ Connector supports mapping individual fields from https://avro.apache.org/docs/1.8.1/gettingstartedjava.html[Avro] formatted key or values.
 
 In this example, the key is a basic string and the value is Avro format.
diff --git a/modules/ROOT/pages/cfgPulsarMapJson.adoc b/modules/ROOT/pages/cfgPulsarMapJson.adoc
@@ -1,5 +1,7 @@
 = 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™ Connector mapping can include individual fields in the JSON structure.
 
 NOTE: JSON records in Pulsar can also have a schema associated with them.
diff --git a/modules/ROOT/pages/cfgPulsarMapKeyPair.adoc b/modules/ROOT/pages/cfgPulsarMapKeyPair.adoc
@@ -1,5 +1,7 @@
 = 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.
 
 For example, the Pulsar world topic (`world_topic`) contains 5 records with a key-value pair in each.
diff --git a/modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc b/modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc
@@ -1,5 +1,7 @@
 = Mapping a topic to multiple tables 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 The DataStax Apache Pulsar™ Connector allows for mapping a single topic to multiple tables for a single connector instance.
 
 In the example `stocks_topic`, the key is a basic string and the value is regular JSON.
diff --git a/modules/ROOT/pages/cfgPulsarMapTopicTable.adoc b/modules/ROOT/pages/cfgPulsarMapTopicTable.adoc
@@ -1,5 +1,7 @@
 = Mapping pulsar topics to database tables 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 DataStax Apache Pulsar™ 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™ Connector can capture multiple topics and supports mapping a single topic to one or more tables.
 
 == DataStax Apache Pulsar™ Connector topic mapping
diff --git a/modules/ROOT/pages/cfgPulsarMapUdt.adoc b/modules/ROOT/pages/cfgPulsarMapUdt.adoc
@@ -1,5 +1,7 @@
 = Mapping messages to table that has a User Defined Type 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 The DataStax Apache Pulsar™ Connector processes JSON, Avro, and complex types directly into a link: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.
 
 In the example `stocks_topic`, the key is a basic string and the value is regular JSON.
diff --git a/modules/ROOT/pages/cfgPulsarMultTopicToTables.adoc b/modules/ROOT/pages/cfgPulsarMultTopicToTables.adoc
@@ -1,5 +1,7 @@
 = Multiple topics to multiple tables 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 The DataStax Apache Pulsar™ Connector allows for mapping multiple topics to multiple tables in a single connector instance.
 
 NOTE: Most Apache Pulsar™ systems store all messages in the same format and DataStax Apache Pulsar™ Connect workers only support a single converter class for key and value.
diff --git a/modules/ROOT/pages/cfgPulsarNowFunction.adoc b/modules/ROOT/pages/cfgPulsarNowFunction.adoc
@@ -1,5 +1,7 @@
 = The now() function in mappings 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 In the Apache Pulsar™ topic mapping, you can use the ``now()``function.
 It returns `TIMEUUID`, which is documented in the link:https://docs.datastax.com/en/dse/6.8/cql/cql/cql_using/refTimeUuidFunctions.html[UUID and timeuuid column].
 
diff --git a/modules/ROOT/pages/cfgPulsarRecordHeaderToTable.adoc b/modules/ROOT/pages/cfgPulsarRecordHeaderToTable.adoc
@@ -1,5 +1,7 @@
 = Extract Pulsar record header values 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 In the Apache Pulsar™ topic mapping, you can extract values from the message properties, and write the values to a xref:index.adoc#supported-databases[supported database table].
 
 For example:
diff --git a/modules/ROOT/pages/cfgPulsarSelectiveUpdateMapsAndUdts.adoc b/modules/ROOT/pages/cfgPulsarSelectiveUpdateMapsAndUdts.adoc
@@ -1,5 +1,7 @@
 = Selectively update maps and UDTs based on Pulsar fields 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 In the Apache Pulsar™ 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`.
 
 The goal is to minimize tombstones in the database. If Maps or UDTs are in the database table that the DataStax Apache Pulsar™ Connector is configured to write to, in order to minimize tombstones, you can use the CQL command `UPDATE` to only update the fields present in the Pulsar record if the `nullToUnset` parameter is set to `true`.
diff --git a/modules/ROOT/pages/cfgPulsarSettingJavaDriverConfig.adoc b/modules/ROOT/pages/cfgPulsarSettingJavaDriverConfig.adoc
@@ -1,5 +1,7 @@
 = Pass Pulsar Connector settings directly to the DataStax Java driver 
 
+:page-tag: pulsar-connector,dev,develop,pulsar,java
+
 In your DataStax Apache Pulsar™ Connector configuration file, you can directly pass settings to the DataStax Java driver by using the `datastax-java-driver` prefix.
 For example:
 
diff --git a/modules/ROOT/pages/cfgPulsarSettingRowLevelTtl.adoc b/modules/ROOT/pages/cfgPulsarSettingRowLevelTtl.adoc
@@ -1,5 +1,7 @@
 = Setting row-level TTL values from Pulsar fields 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 In the Apache Pulsar™ 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.
 The mapping setting provides a special property, `__ttl`.
 The format is:
diff --git a/modules/ROOT/pages/cfgPulsarStringJson.adoc b/modules/ROOT/pages/cfgPulsarStringJson.adoc
@@ -1,5 +1,7 @@
 = 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™ connector mapping can include individual fields in the JSON structure.
 
 In the following example, the key is text field and the value is JSON.
diff --git a/modules/ROOT/pages/cfgRefPulsarAuth.adoc b/modules/ROOT/pages/cfgRefPulsarAuth.adoc
@@ -1,5 +1,7 @@
 = Using the DataStax Apache Pulsar™ Connector with DataStax Enterprise authentication 
 
+:page-tag: pulsar-connector,security,secure,pulsar
+
 When authentication is enabled, provide credentials for internal authentication or LDAP.
 
 When link:https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/security/secAuthTOC.html[authentication] is enabled, provide credentials for internal authentication, LDAP, or location of the Kerberos keytab file.
diff --git a/modules/ROOT/pages/cfgRefPulsarAuthLdap.adoc b/modules/ROOT/pages/cfgRefPulsarAuthLdap.adoc
@@ -1,5 +1,7 @@
 = 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™ Connector.
 A login role for the connector with access to the mapped tables is also required.
 
diff --git a/modules/ROOT/pages/cfgRefPulsarConnector.adoc b/modules/ROOT/pages/cfgRefPulsarConnector.adoc
@@ -1,5 +1,7 @@
 = DataStax Apache Pulsar™ Connector details
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 Set the common DataStax Apache Pulsar™ Connector parameters.
 
 == Parameters 
diff --git a/modules/ROOT/pages/cfgRefPulsarDates.adoc b/modules/ROOT/pages/cfgRefPulsarDates.adoc
@@ -1,5 +1,7 @@
 = 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.
 
 [source,language-yaml]
diff --git a/modules/ROOT/pages/cfgRefPulsarDseConnection.adoc b/modules/ROOT/pages/cfgRefPulsarDseConnection.adoc
@@ -1,5 +1,7 @@
 = DataStax connection 
 
+:page-tag: pulsar-connector,admin,dev,connect,pulsar
+
 Configure the connection settings from Apache Pulsar™ to the cluster.
 
 == Parameters
diff --git a/modules/ROOT/pages/cfgRefPulsarDseTable.adoc b/modules/ROOT/pages/cfgRefPulsarDseTable.adoc
@@ -1,5 +1,7 @@
 = Pulsar topic-to-table settings 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 Capture Apache Pulsar™ 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.
 
 == Parameters
diff --git a/modules/ROOT/pages/cfgRefPulsarSsl.adoc b/modules/ROOT/pages/cfgRefPulsarSsl.adoc
@@ -1,5 +1,7 @@
 = SSL encrypted connection 
 
+:page-tag: pulsar-connector,security,secure,pulsar
+
 When the cluster has client encryption enabled, configure the SSL keys and certificates for the DataStax Apache Pulsar™ Connector.
 
 TIP: SSL encryption settings are configured in the link:https://docs.datastax.comen/dse/6.8//dse-admin/datastax_enterprise/config/configCassandra_yaml.html#configCassandra_yaml__clientEncryptSection[Client-to-node encryption options].
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -1,5 +1,7 @@
 = About the DataStax Apache Pulsar™ Connector 
 
+:page-tag: pulsar-connector,planner,dev,admin,pulsar
+
 DataStax Apache Pulsar™ Connector is open-source software (OSS) installed in the Pulsar IO framework, and synchronizes records from a Pulsar topic with table rows in DataStax Enterprise (DSE) and Cassandra databases.
 
 == Key Features
diff --git a/modules/ROOT/pages/monPulsarConnectMetrics.adoc b/modules/ROOT/pages/monPulsarConnectMetrics.adoc
@@ -1,5 +1,7 @@
 = DataStax Apache Pulsar™ Connector metrics 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 You can view DataStax Apache Pulsar™ Connector metrics in raw Prometheus format at the Apache Pulsar metrics endpoint:
 
 [source,no-highlight]
diff --git a/modules/ROOT/pages/opsPulsarAboutOperations.adoc b/modules/ROOT/pages/opsPulsarAboutOperations.adoc
@@ -1,5 +1,7 @@
 = About operating and maintaining the DataStax Connector 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 To operate and maintain the DataStax Apache Pulsar™ Connector use the Apache Pulsar™ adminstration tool, `pulsar-admin` in concert with the Apache Pulsar™ REST Administration API.
 
 For more information on `pulsar-admin`, see link:http://pulsar.apache.org/tools/pulsar-admin/2.7.0-SNAPSHOT/#topics[Apache Pulsar Admin Tool Documentation].
diff --git a/modules/ROOT/pages/opsPulsarAddField.adoc b/modules/ROOT/pages/opsPulsarAddField.adoc
@@ -1,5 +1,7 @@
 = Adding a field to a Pulsar Topic 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 Use these steps to write a new field to an existing xref:index.adoc#supported-databases[supported database] table column.
 
 . In the DataStax Apache Pulsar™ Connector configuration file, add the field-to-column definition.
diff --git a/modules/ROOT/pages/opsPulsarAddTableColumn.adoc b/modules/ROOT/pages/opsPulsarAddTableColumn.adoc
@@ -1,5 +1,7 @@
 = Adding a column to the database table 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 Add a column to the xref:index.adoc#supported-databases[supported database] table to synchronize an existing field from a Pulsar topic.
 
 . On a database node, use link:https://docs.datastax.com/en/dse/6.8/cql/cql/cql_reference/cql_commands/cqlAlterTable.html[ALTER TABLE] to add the column to the table.
diff --git a/modules/ROOT/pages/opsPulsarChangeSchema.adoc b/modules/ROOT/pages/opsPulsarChangeSchema.adoc
@@ -1,5 +1,7 @@
 = Changing the topic or table schema 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 How to update the DataStax Apache Pulsar™ Connector when schema changes are required.
 
 * xref:opsPulsarAddField.adoc[] Add a field Pulsar Topic schema.
diff --git a/modules/ROOT/pages/opsPulsarConnectorStatus.adoc b/modules/ROOT/pages/opsPulsarConnectorStatus.adoc
@@ -1,5 +1,7 @@
 = Getting the DataStax Connector status 
 
+:page-tag: pulsar-connector,dev,develop,admin,manage,pulsar
+
 Use the Apache Pulsar™ administration tool `sinks status` command to display the status of the DataStax Apache Pulsar™ Connector.
 
 [source,language-bash]
diff --git a/modules/ROOT/pages/opsPulsarDeleteConnector.adoc b/modules/ROOT/pages/opsPulsarDeleteConnector.adoc
@@ -1,5 +1,7 @@
 = Deleting the DataStax Apache Pulsar™ Connector 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 To completely remove the DataStax Apache Pulsar™ Connector:
 
 . Delete any sinks associated with the DataStax Apache Pulsar™ Connector:
diff --git a/modules/ROOT/pages/opsPulsarDisplayConfig.adoc b/modules/ROOT/pages/opsPulsarDisplayConfig.adoc
@@ -1,5 +1,7 @@
 = Displaying the DataStax Apache Pulsar™ Connector configuration 
 
+:page-tag: pulsar-connector,dev,develop,admin,manage,pulsar
+
 Use the Apache Pulsar™ administration tool sinks command to retrieve detailed information on a Pulsar sink:
 
 [source,language-bash]
diff --git a/modules/ROOT/pages/opsPulsarRemoveColumn.adoc b/modules/ROOT/pages/opsPulsarRemoveColumn.adoc
@@ -1,5 +1,7 @@
 = Removing a Table Column from the mapping specification 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 Remove a xref:index.adoc#supported-databases[supported database] table column.
 
 . Remove the field to column mapping from the configuration. See xref:cfgPulsarMapTopicTable.adoc[].
diff --git a/modules/ROOT/pages/opsPulsarRemoveField.adoc b/modules/ROOT/pages/opsPulsarRemoveField.adoc
@@ -1,5 +1,7 @@
 = Removing a field map 
 
+:page-tag: pulsar-connector,dev,develop,pulsar
+
 DataStax Apache Pulsar™ Connector processing fails if any mapped Pulsar topic fields are missing from the record.
 If a field is missing or if the schema change is known ahead, remove the topic-column mapping.
 
diff --git a/modules/ROOT/pages/opsPulsarRestart.adoc b/modules/ROOT/pages/opsPulsarRestart.adoc
@@ -1,5 +1,7 @@
 = Restarting the DataStax Apache Pulsar™ Connector 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 To restart a DataStax Apache Pulsar™ Connector that was previously running, use the `pulsar-admin sinks` command:
 
 [source,language-bash]
diff --git a/modules/ROOT/pages/opsPulsarScaling.adoc b/modules/ROOT/pages/opsPulsarScaling.adoc
@@ -1,5 +1,7 @@
 = Scaling the DataStax Apache Pulsar™ Connector 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 Use the Apache Pulsar™ administration tool to increase or decrease the number of workers to run for a given sink using the parallelism factor. You can specify the parallelism factor during creation of a Pulsar sink, and you can modify it after the fact as well. The default parallelism factor is `1`.
 
 == Configuring parallelism during sink creation
diff --git a/modules/ROOT/pages/opsPulsarUpdateConfig.adoc b/modules/ROOT/pages/opsPulsarUpdateConfig.adoc
@@ -1,5 +1,7 @@
 = Updating the DataStax Apache Pulsar™ Connector configuration 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 To update the configuration of an active DataStax Apache Pulsar™ Connector sink, use the  Apache Pulsar™ `pulsar-admin sinks update` command:
 
 [source,language-bash]
diff --git a/modules/ROOT/pages/pulsarInstall.adoc b/modules/ROOT/pages/pulsarInstall.adoc
@@ -1,5 +1,7 @@
 = Installing DataStax Apache Pulsar™ Connector 
 
+:page-tag: pulsar-connector,admin,dev,install,pulsar
+
 Install DataStax Apache Pulsar™ Connector from the DataStax distribution tar file using an account that has write access to the Pulsar configuration directory.
 
 The supported operating systems are Linux and macOS.
diff --git a/modules/ROOT/pages/pulsarQuickStart.adoc b/modules/ROOT/pages/pulsarQuickStart.adoc
@@ -1,5 +1,7 @@
 = Pulsar Connector single instance quick start 
 
+:page-tag: pulsar-connector,dev,admin,planner,quickstart,pulsar
+
 This quick start will walk you through the simplest possible configuration connecting a standalone Apache Pulsar™ instance to a single standalone DataStax Enterprise (DSE) 6.8 node.
 
 Once you've configured Pulsar, a Pulsar sink, the DataStax Apache Pulsar™ Connector and the DSE instance, you'll be able to send simple key/value pair messages using the Pulsar client utility, `pulsar-client` and retrieve them from a DSE keyspace and table.
diff --git a/modules/ROOT/pages/pulsarSizing.adoc b/modules/ROOT/pages/pulsarSizing.adoc
@@ -1,5 +1,7 @@
 = System requirements 
 
+:page-tag: pulsar-connector,planner,plan,pulsar
+
 The system requirements for DataStax Apache Pulsar™ Connector depends on the workload and network capacity. The factors include characteristics of the Pulsar topic and the cluster data models and volume. DataStax recommends testing with realistic data flows before committing to an instance type for the connector.
 
 DataStax Apache Pulsar™ Connector is bound by the amount of CPU available on the host. The connector holds all the records pulled from Pulsar topics in memory, along with the cluster metadata and prepared statements.
diff --git a/modules/ROOT/pages/secPulsarInternalLdapAuth.adoc b/modules/ROOT/pages/secPulsarInternalLdapAuth.adoc
@@ -1,5 +1,7 @@
 = Using internal or LDAP authentication 
 
+:page-tag: pulsar-connector,security,secure,pulsar,ldap
+
 Authenticate the DataStax Apache Pulsar™ Connector session using internal or LDAP authentication.
 When the cluster has internal or LDAP authentication enabled, configure the user name and password settings for DataStax Apache Pulsar™ Connector.
 This task also requires a login role for the DataStax Apache Pulsar™ Connector with access to the mapped tables.
diff --git a/modules/ROOT/pages/trbPulsarTsLargeBatches.adoc b/modules/ROOT/pages/trbPulsarTsLargeBatches.adoc
@@ -1,5 +1,7 @@
 = Writing fails because of mutation size 
 
+:page-tag: pulsar-connector,planner,plan,pulsar
+
 The DataStax Apache Pulsar™ Connector collects records to write to the DataStax Enterprise (DSE) database in CQL link:https://docs.datastax.com/en/dse/6.8/cql/cql/cql_reference/cql_commands/cqlBatch.html[BATCH] commands.
 Data insertions and deletions in the records are known as mutations.
 The Connector is implemented to use single-partition batches that are submitted as one mutation operation.
diff --git a/modules/ROOT/pages/trbPulsarTsLoadBalancing.adoc b/modules/ROOT/pages/trbPulsarTsLoadBalancing.adoc
@@ -1,5 +1,7 @@
 = Loading balancing datacenter is not specified 
 
+:page-tag: pulsar-connector,admin,manage,pulsar
+
 The following error message occurs when the load balancing datacenter (xref:cfgRefPulsarDseConnection.adoc#loadBalancing[loadBalancing.localDc]) is not set in the configuration file.
 
 [source,no-highlight]
diff --git a/modules/ROOT/pages/trbPulsarTsRecordFailsToWriteToTable.adoc b/modules/ROOT/pages/trbPulsarTsRecordFailsToWriteToTable.adoc
@@ -1,5 +1,7 @@
 = Record fails to write 
 
+:page-tag: pulsar-connector,dev,develop,admin,manage,pulsar
+
 Records never appear in the DataStax Enterprise (DSE) database table. The cause can be issues with node availability, transient errors that prevent writes due to consistency level, a schema change where a mapped column was removed from the target table, and so forth.
 
 == Remediation
diff --git a/modules/ROOT/pages/trbPulsarTsRecordParsingFails.adoc b/modules/ROOT/pages/trbPulsarTsRecordParsingFails.adoc
@@ -1,5 +1,7 @@
 = Data parsing fails 
 
+:page-tag: pulsar-connector,dev,develop,admin,manage,pulsar
+
 When the data from an Apache Pulsar™ field is not compatible with the data type of the target xref:index.adoc#supported-databases[supported database] table column, the data conversion fails and a message is logged in the Pulsar Connect log.
 
 Example error message when parsing a string value for a numeric column:
