Mapping basic messages to table columns
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.
The key is an integer and the value is text.
Table requirements
-
Ensure the following when mapping fields to columns:
-
Data in the Pulsar field is compatible with the database table column data type.
-
Pulsar field mapped to a database primary key (PK) column always contains data. Null values are not allowed in PK columns.
-
-
Set up the supported database table.
-
Create the keyspace. Ensure that keyspace is replicated to a datacenter that is set in the DataStax Apache Pulsar Connector contactPoints parameter. For example, create the world_keyspace:
cqlsh -e "CREATE KEYSPACE world_keyspace WITH replication = {'class': 'NetworkTopologyStrategy','Cassandra': 1};"The datacenter name is case sensitive. Use nodetool ring to get a list of datacenters. -
Create the table. For example, create the world\_table:
cqlsh -e "CREATE TABLE world_table (recordid int PRIMARY KEY, continent text);" -
Verify that all nodes have the same schema version using [nodetool describering](https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/tools/nodetool/toolsDescribeRing.html). Replace keyspace_name:
nodetool describering -- keyspace_name -
In the DataStax Apache Pulsar™ Connector configuration file:
-
Add the topic name to topics.
-
Define the topic-to-table map prefix.
-
Define the field-to-column map.
Example configurations for
world_topictoworld_tableusing the minimum required settings:tasks.max: 1 topics: world_topic topic: world_topic: world_keyspace: world_table: mapping: 'recordid=key, continent=value'
-
