--- schema_version: "1" id: 61248247f70f80fc9ca6088ffa21aec715b1903b474cd36488c761918560b243 title: Apache Cassandra Connector 5.0 Examples collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cassandra-connector/latest/cassandra-connector-examples.md canonical_url: https://docs.mulesoft.com/cassandra-connector/latest/cassandra-connector-examples source_site: docs.mulesoft.com content_type: documentation content_hash: 5064f6869183cd09c9cf41f598d922e8330fc3c3ee404778f5b098bd4cb65348 description: MuleSoft Documentation Site release: "5.0" latest: true --- --- product: Apache Cassandra Connector version: 5.0 is-latest-version: true --- # Apache Cassandra Connector 5.0 Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The following examples show how to configure Apache Cassandra Connector: - [Create a New Apache Cassandra Table](#create-table) Creates a template for an HTML form to use to enter data for the new table, creates a keyspace for the new table, and then creates the table - [Manipulate Data in an Apache Cassandra Database](#manipulate-data) Gets table names from a keyspace, performs operations on tables and table columns, executes Cassandra Query Language (CQL) queries, and so on. ## Create a New Apache Cassandra Table This example contains the following flows: - The first flow configures a template for the HTML input form used to convey data for the new table. - The second flow creates the keyspace for the new table. - The third flow creates the new table. This example uses variables for some field values. You can either: - Replace the variables with their values in the code - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see Configuring Property Placeholders. ### Configure a Template for the HTML Input Form This flow configures an HTML template to use for providing HTML input to create the new table: ![Parse Template Flow](/mulesoft/current/en-us/cassandra-connector/latest/_images/cassandra-parse-template.png) Figure 1. Flow for configuring an HTML template #### Configure HTTP Listener Configure HTTP Listener to initiate a Mule flow when a call is made to the `/` path on port 8081: 1. Create a new Mule Project in Anypoint Studio. 2. In Studio, click **HTTP** and drag the **Listener** operation to the canvas. 3. On the **Listener** properties window, click the plus sign (**+**) next to the **Connector configuration** field to add a global element. 4. Accept the defaults. 5. On the **Listener** properties window, set the **Path** field value to `/`. #### Add a Parse Template Component Add a **Parse Template** component to create a template for an HTML form (`form.html`), which is located in the main resources folder. The example uses this form to convey information for creating the table. 1. From the Mule Palette view, search for `parse` and drag **Core** > **Parse Template** to the right of **Listener**. 2. In the **Location** field, enter `form.html`. ### Create the Keyspace This flow creates the keyspace for the new table: ![Create keyspace flow](/mulesoft/current/en-us/cassandra-connector/latest/_images/cassandra-create-keyspace.png) Figure 2. Flow for creating a keyspace #### Configure HTTP listener Configure HTTP Listener to initiate a Mule flow when a call is made to the `/test/createKeyspace` path on port `8081`: 1. Create a new Mule Project in Anypoint Studio. 2. In Studio, click **HTTP** and drag the **Listener** operation to the canvas. 3. On the Listener properties window, click the plus sign **+** next to the **Connector configuration** field to add a global element. 4. Accept the defaults. 5. In **Listener** configuration window, set the **Path** field value to `/test/createKeyspace`. #### Add a Transform Message Component Add a **Transform Message** component to set Java variables based on the payload received from **HTTP Listener**: 1. From the Mule Palette view, drag a **Transform Message** component to the right of **Listener**. 2. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```dataweave %dw 2.0 output application/java --- { "keyspaceName": payload.keyspaceName, "replicationFactor": payload.replicationFactor, "replicationStrategyClass": payload.replicationStrategyClass } as Object { class: "com.mulesoft.connector.cassandradb.api.CreateKeyspaceInput" } ``` #### Add the Create Keyspace Operation Add the **Create keyspace** operation to create the keyspace where the new table will reside: 1. From the **Mule Palette** view, select **CassandraDB** and drag the **Create keyspace** operation to the right of the **Transform Message** component. 2. In the **Create keyspace** configuration, click the plus sign (**+**) next to the **Connector configuration** field to add a global element. 3. Configure the fields in the global element:
FieldDescription

Host

${cassandra.Host}

Port

${cassandra.Port}

Cassandra Keyspace

${cassandra.keySpace}

Username

${cassandra.userName}

Password

${cassandra.password}

On the **Advanced Settings** tab, set **Local Datacenter** when contact points don’t share one datacenter:
FieldDescription

Local Datacenter

${cassandra.localDatacenter}

4. Click **Test Connection** to confirm that Mule can connect with the target Apache Cassandra instance. If the connection is successful, click **OK** to save the configuration. Otherwise, review and correct any invalid parameters and retest. 5. Save the project. 6. Test the app by sending a REST request to the `test/createKeyspace` path on port `8081`. ### Create a New Table This flow creates a new table in the target Apache Cassandra database: ![Create table flow](/mulesoft/current/en-us/cassandra-connector/latest/_images/cassandra-create-table.png) Figure 3. Flow for creating a new table #### Configure HTTP Listener Configure HTTP Listener to initiate a Mule flow when a call is made to the `/test/createTable` path on port `8081`: 1. Create a new Mule Project in Studio. 2. In Studio, click **HTTP** and drag the **Listener** operation to the canvas. 3. In the **Listener** configuration, click the plus sign **+** next to the **Connector configuration** field to add a global element. 4. Accept the defaults. 5. In the **Listener** configuration, set the **Path** field value to `/test/createTable`. ### Add a Transform Message Component Add a **Transform Component** to set Java variables based on the payload received from **HTTP Listener**: 1. From the Mule Palette view, drag a **Transform Message** component to the right of **Listener**. 2. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```dataweave %dw 2.0 output application/java --- { "columns": payload.columns, "tableName": payload.tableName, "keyspaceName": payload.keyspaceName } as Object { class : "com.mulesoft.connector.cassandradb.api.CreateTableInput" } ``` #### Add the Create Table Operation Add a **Create Table** operation to create a new table in the keyspace you created in the previous flow: 1. From the **Mule Palette** view, select **CassandraDB** and drag the **Create Table** operation to the right of the **Transform Message** component. 2. In the **Create Table** configuration, click the plus sign (**+**) next to the **Connector configuration** field. 3. Select the global element that you configured for the **Create keyspace** operation. 4. Click **OK**. 5. Click **Test Connection** to confirm that Mule can connect with the Cassandra instance. If the client test is successful, click **OK** to save the configuration. Otherwise, review and correct any invalid parameters and retest. 6. Save and run the Mule app. 7. Test the app by sending a **POST** command to the `/test/createTable` path on port `8081`. Use the `application/json` MIME type and enter the table description in the command body, using uppercase for the data types: ```text { "tableName": "users", "keyspaceName": "Excelsior", "columns": [ { "name": "id", "type": "INT", "primaryKey": "true" }, { "name": "username", "type": "TEXT", "primaryKey": "true" }, { "name": "name", "type": "TEXT", "primaryKey": "false" }, { "name": "email", "type": "TEXT", "primaryKey": "false" } ] } ``` ### XML for the Create an Apache Cassandra Keyspace and Table Example Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule app: ```xml ``` ## Manipulate Data in an Apache Cassandra Database This example shows the following ways to manipulate data in an Apache Cassandra database: - [Get table names from a keyspace.](#get-table-names) - Perform the following CRUD operations on data in an Apache Cassandra table: - [Insert](#insert) - [Select](#select) - [Update](#update) - [Delete](#delete) - Perform the following operations on an Apache Cassandra table column: - [Delete the column’s value.](#delete-columns) - [Rename a column.](#rename-columns) - [Add a new column.](#add-new-column) - [Drop a column.](#drop-columns) - [Execute a Cassandra Query Language (CQL) query.](#execute-cql) - Drop data from the Apache Cassandra database table: - [Drop a table from a keyspace.](#drop-table) - [Drop a keyspace.](#drop-keyspace) ### Get Table Names from a Keyspace This Mule flow returns all table names from the specified keyspace. ![Studio flow for the Get table names from keyspace operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/get-table-names.png) In this flow, you configure: - An **HTTP Listener** component - A **Get table names from keyspace** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/getTablesFromKeyspace`. #### Add the Get Table Names from Keyspace Operation The **Get table names from keyspace** operation returns all table names from the specified keyspace. 1. Drag the **Get table names from keyspace** operation onto the canvas, next to **HTTP Listener**. 2. In the **Get table names from keyspace** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Get table names from keyspace** properties window:
FieldValue

Keyspace name

#[payload.keyspaceName]

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Get table names from keyspace**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Insert This Mule flow inserts entities in a table in a keyspace. ![Studio flow for the Insert Entity operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/insert-entity.png) In this flow, you configure: - An **HTTP Listener** component - A **Transform Message** component - An **Insert Entity** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/insert`. #### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace to Java. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **HTTP Listener**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "id": payload.id, "name": payload.name, "event": payload.event } ``` #### Add the Insert Entity Operation The **Insert Entity** operation inserts entities into a table in a keyspace. 1. Drag the **Insert Entity** operation onto the canvas, next to **Transform Message**. 2. In the **Insert Entity** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Insert Entity** properties window:
FieldValue

Table

example_table

Keyspace name

example_keyspace

Entity to insert

payload

#### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Insert Entity**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Select This Mule flow executes a **Select** query. ![Studio flow for the Select operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/select.png) In this flow, you configure: - An **HTTP Listener** component - A **Select** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/insert`. #### Add the Select Operation The **Select** operation executes a **Select** query on the keyspace. 1. Drag the **Select** operation onto the canvas, next to **HTTP Listener**. 2. In the **Select** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Select** properties window:
FieldValue

Query

SELECT id, name, event FROM example_keyspace.example_table

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Select**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Update This Mule flow updates entities in a table in a keyspace. ![Studio flow for the Update Entity operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/update-entity.png) In this flow, you configure: - An **HTTP Listener** component - A **Transform Message** component - An **Update Entity** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/update`. #### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace to Java. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **HTTP Listener**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "where":{ id: payload.where }, "columns":payload.columns } ``` #### Add the Update Entity Operation The **Update Entity** operation inserts entities into a table in a keyspace. 1. Drag the **Update Entity** operation onto the canvas, next to **Transform Message**. 2. In the **Update Entity** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Update Entity** properties window:
FieldValue

Table

example_table

Keyspace name

example_keyspace

Entity to insert

payload

#### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Update Entity**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Delete This Mule flow deletes a record from a table in a keyspace. ![Studio flow for the Delete Rows operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/delete-row.png) In this flow, you configure: - An **HTTP Listener** component - A **Transform Message** component - A **Delete Rows** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/deleteRows`. #### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **HTTP Listener**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "where": { id: payload.ids } } ``` #### Add the Delete Rows Operation The **Delete Rows** operation deletes a record. 1. Drag the **Delete Rows** operation onto the canvas, next to **Transform Message**. 2. In the **Delete Rows** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Delete Rows** properties window:
FieldValue

Table

example_table

Keyspace name

example_keyspace

Entity to insert

payload

#### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Delete Rows**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Delete Columns This Mule flow deletes a column’s value from a table in a keyspace. ![Studio flow for the Delete Columns Value operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/delete-column.png) In this flow, you configure: - An **HTTP Listener** component - A **Transform Message** component - An **Delete Columns Value** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/deleteColumns`. #### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace to Java. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **HTTP Listener**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "columns": payload.columns, "where": { id:payload.where } } ``` #### Add the Delete Columns Value Operation The **Delete Columns Value** operation deletes values from an object specified by the **Where clause** field. 1. Drag the **Delete Columns Value** operation onto the canvas, next to **Transform Message**. 2. In the **Delete Columns Value** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Delete Columns Value** properties window:
FieldValue

Table

example_table

Keyspace name

example_keyspace

Entities

Edit inline

Value

#[payload.entities]

Where clause

payload

#### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Delete Columns Value**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Rename Columns This Mule flow renames a column in a table in the specified keyspace. ![Studio flow for the Rename Column operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/rename-columns.png) In this flow, you configure: - An **HTTP Listener** component - A **Rename Column** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/renameColumn`. #### Add the Rename Column Operation The **Rename Column** operation renames a column in a table in a keyspace. 1. Drag the **Rename Column** operation onto the canvas, next to **HTTP Listener**. 2. In the **Rename Column** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Rename Column** properties window:
FieldValue

Table

#[payload.tableName]

Keyspace name

#[payload.keyspaceName]

Old column name

payload.oldName

New column name

#[payload.newName]

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Rename Column**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Add New Columns This Mule flow adds a new column to a table in a keyspace. ![Studio flow for the Add New Table Column operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/add-new-column.png) In this flow, you configure: - An **HTTP Listener** component - A **Set Variable** component - A second **Set Variable** component - A **Transform Message** component - An **Add New Table Column** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/addNewColumn`. #### Add the Set Variable Component The first **Set Variable** component stores a value for the table name. 1. In the **Mule Palette** view, search for `set variable`. 2. Drag the **Set Variable** component onto the canvas, next to **HTTP Listener**. 3. Configure the following fields in the **Set Variable** properties window:
FieldValue

Name

tableName

Value

#[payload.tableName]

#### Add the Second Set Variable Component The second **Set Variable** component stores a value for the keyspace name. 1. In the **Mule Palette** view, search for `set variable`. 2. Drag the **Set Variable** component onto the canvas, next to **HTTP Listener**. 3. Configure the following fields in the **Set Variable** properties window:
FieldValue

Name

keyspaceName

Value

#[payload.keyspaceName]

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Set Variable**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "column": payload.column, "type": payload.'type' } as Object { class : "com.mulesoft.connector.cassandradb.api.AlterColumnInput" } ``` #### Add the Add New Table Column Operation The **Add New Table Column** operation adds a new column. 1. Drag the **Add New Table Column** operation onto the canvas, next to **Transform Message**. 2. In the **Add New Table Column** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Add New Table Column** properties window:
FieldValue

Table

#[vars['tableName']]

Keyspace name

#[vars['keyspaceName']]

Alter column input

payload

#### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Add New Table Column**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Drop Columns This Mule flow removes a column from a table in a keyspace. ![Studio flow for the Drop Column operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/drop-columns.png) In this flow, you configure: - An **HTTP Listener** component - A **Drop Column** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/dropColumn`. #### Add the Drop Column Operation The **Drop Column** operation removes a column. 1. Drag the **Drop Column** operation onto the canvas, next to **HTTP Listener**. 2. In the **Drop Column** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Drop Column** properties window:
FieldValue

Table

#[payload.tableName]

Keyspace name

#[payload.keyspaceName]

Column name

payload.columnName

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Drop Column**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Execute a Cassandra Query Language (CQL) Query This Mule flow executes the specified raw input query. ![Studio flow for the Execute CQL Query operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/execute-cql.png) In this flow, you configure: - An **HTTP Listener** component - A **Transform Message** component - An **Execute CQL Query** operation - A second **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/executeCqlQuery`. #### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace to Java. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **HTTP Listener**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/java --- { "cqlQuery": payload.cqlQuery, "parameters": payload.parameters } as Object { class : "com.mulesoft.connector.cassandradb.api.CQLQueryInput" } ``` #### Add the Execute CQL Query Operation The **Execute CQL Query** operation executes the raw input query. 1. Drag the **Execute CQL Query** operation onto the canvas, next to **Transform Message**. 2. In the **Execute CQL Query** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. #### Add the Second Transform Message Component The second **Transform Message** component converts the data from the keyspace from Java to XML. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Execute CQL Query**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Drop Table This Mule flow drops a table from the specified keyspace. ![Studio flow for the Drop Table operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/drop-table.png) In this flow, you configure: - An **HTTP Listener** component - A **Drop Table** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/dropTable`. #### Add the Drop Table Operation The **Drop Table** operation drops a table from the specified keyspace. If no keyspace is specified for the **Drop Table** operation, the table is created in the keyspace in the connection parameters. 1. Drag the **Drop Table** operation onto the canvas, next to **HTTP Listener**. 2. In the **Drop Table** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Drop Table** properties window:
FieldValue

Table name

payload.tableName

Keyspace name

#[payload.keyspaceName]

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Drop Table**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### Drop Keyspace This Mule flow drops the specified keyspace and its values. ![Studio flow for the Drop Keyspace operation](/mulesoft/current/en-us/cassandra-connector/latest/_images/drop-keyspace.png) In this flow, you configure: - An **HTTP Listener** component - A **Drop Keyspace** operation - A **Transform Message** component #### Configure HTTP Listener Configure **HTTP Listener** to initiate a Mule flow when a call is made to the `/` account path on `localhost`, port `8081`. This example uses variables for some field values. You can either: - Replace the variables with their values in the code. - Provide the values for each variable in a properties file and then refer to that file from the connector configuration. If you don’t know how to use a properties file, see [Configuring Property Placeholders](https://docs.mulesoft.com/mule-runtime/latest/mule-app-properties-to-configure). To configure **HTTP Listener**: 1. Create a new Mule project in Studio. 2. In the **Mule Palette** view, search for `http` and select the **Listener** operation: 3. Drag the **Listener** operation onto the canvas. 4. In the **Listener** configuration, click the **Add** icon next to the **Connector configuration** field to add a global element. 5. Click **OK** to accept the defaults. 6. Set the **Path** field to `/dropKeyspace`. #### Add the Drop Keyspace Operation The **Drop Keyspace** operation drops the keyspace and its values. 1. Drag the **Drop Keyspace** operation onto the canvas, next to **HTTP Listener**. 2. In the **Drop Keyspace** configuration, click the **Connector configuration** dropdown and select **CassandraDB\_Config**. 3. Configure the following fields in the **Drop Keyspace** properties window:
FieldValue

Keyspace name

payload.keyspaceName

#### Add the Transform Message Component The **Transform Message** component converts the data from the keyspace. 1. In the **Mule Palette** view, search for `transform message`. 2. Drag the **Transform Message** component onto the canvas, next to **Drop Keyspace**. 3. In the **Transform Message** configuration, overlay the brackets in the **Output** section with this XML: ```xml %dw 2.0 output application/json --- payload ``` ### XML for the Manipulate Data in an Apache Cassandra Database Example Paste this code into the Studio XML editor to quickly load the flow for this example into your Mule app: ```xml SELECT id, name, event FROM example_keyspace.example_table ``` ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com)