Removing a field map

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.

The database table schema has PRIMARY KEY columns that uniquely identify and partition rows. See CQL data modeling. A NULL is not allowed in a PRIMARY KEY column, therefore, each PRIMARY KEY column must have a field-column map.
  1. On a supported database node, use the CQLSH DESCRIBE TABLE command to verify that the field is not a PRIMARY KEY (PK) column.

    If the field is a PK column, map a different field to the column.
  2. Remove the field to column mapping from the configuration. See Mapping pulsar topics to database tables.

  3. Update the configuration with the new settings. See Updating the DataStax Apache Pulsar™ Connector configuration.

  4. Start the Pulsar producer that had the schema change.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,