Datastax Astra Streaming sink connector You can use the Datastax Astra Streaming Connector to get data from or send data to an Astra stream. This topic covers how to configure the DataStax Astra Streaming Connector to send data from Decodable into DataStax Astra. If you are looking for information about how to get data from DataStax Astra into Decodable, see Datastax Astra Streaming source connector in the Connect to a data source chapter. Features Delivery guarantee At least once Compatibility Pulsar 2.9.x or above Steps If you want to use the Decodable CLI or API to create the connection, you can refer to the Property Name column for information about what the underlying property names are. The connector name is astra-streaming. From the Connections page, select the DataStax Astra Streaming Connector and complete the following fields. UI Field Property Name Description Connection Type N/A Select sink to use this connector to send data into DataStax Astra. Broker Service URL service-url The URL to connect to your Astra Streaming broker. For example, pulsar+ssl://broker.example.com:6651. Admin Web Service URL admin-url The URL to connect to your Astra Streaming admin endpoint. For example, <https://broker.example.com>. Topic topic The fully qualified name of the Astra topic. For example, persistent://stream/namespace/topic-name. Authentication Token token The JWT web token to use for authentication. Partition Key Columns key.fields A list of fields, delimited by semicolons, that comprise the partition key. For example: field1;field2. Partition Key Format key.format Optional. The format used to serialize and deserialize the partition key. Must be one of the following: JSON AVRO Raw Value Format format The format for data in the Astra topic. Must be one of the following: JSON AVRO Raw Partition Key Inclusion Policy value.fields-include Specify whether the partition key columns should be present in the payload values sent to Astra. For an example of how the key.fields, key.format, and value.fields-include arguments work together, see the examples in the Key and Value Formats section in the Apache Flink documentation. Select the stream that you’d like to connect to this connector. Then, select Next. Define the connection’s schema. Decodable can automatically populate the connection’s schema using Pulsar’s schema registry. In most cases, you’ll want to select Schema Registry to automatically populate the connection’s schema. However, if you would like to manually enter the schema, select New Schema or Structured Schema Definition. If you want to automatically populate the connection schema using Pulsar’s schema registry, you’ll also need to provide the name of your Pulsar tenant, the namespace where your topic is, and the version of the schema that you’d like to use. Select Next when you are finished providing defining the connection’s schema. Give the newly created connection a Name and Description and select Save. Connector starting state and offsets A new sink connection will start reading from the Latest point in the source Decodable stream. This means that only data that’s written to the stream when the connection has started will be sent to the external system. You can override this when you start the connection to Earliest if you want to send all the existing data on the source stream to the target system, along with all new data that arrives on the stream. When you restart a sink connection it will continue to read data from the point it most recently stored in the checkpoint before the connection stopped. You can also opt to discard the connection’s state and restart it afresh from Earliest or Latest as described above. Learn more about starting state here.