# Sinks Sink connectors read data from Kafka and write to an external system. ***
Cover image
AWS S3Sink data from Kafka to AWS S3 including backing up topics and offsets.Connectors -- AWS S3.pngaws-s3
Azure CosmosDBSink data from Kafka to Azure CosmosDB.Connectors -- Azure CosmoDB.pngazure-cosmosdb
Azure Data Lake Gen 2Sink data from Kafka to Azure Data Lake Gen 2Connectors -- Azure Data Lake Gen 2.png
Azure Event HubsLoad data from Azure Event Hubs into Kafka topics.Connectors -- Azure Event Hubs.pngazure-event-hubs
Azure Service BusSink data from Kafka to Azure Service Bus topics and queues.Connectors -- Azure Service Bus.pngazure-service-bus
CassandraSink data from Kafka to Cassandra.Connectors -- Cassandra.pngcassandra
ElasticsearchSink data from Kafka to Elasticsearch.Connectors -- Elasticsearch.pngelasticsearch
GCP Big QuerySink data from Kafka to Big Query
GCP StorageSink data from Kafka to GCP Storage.Connectors -- GCP Storage.pnggcp-storage
HTTP SinkSink data from Kafka to a HTTP endpoint.Connectors -- HTTP Sink.pnghttp
InfluxDBSink data from Kafka to InfluxDB.Connectors -- Influx DB.pnginfluxdb
JMSSink data from Kafka to JMS.Connectors -- JMS.pngjms
MongoDBSink data from Kafka to MongoDB.Connectors -- MongoDB.pngmongodb
MQTTSink data from Kafka to MQTT.Connectors --MQTT.pnghttps://docs.lenses.io/latest/connectors/kafka-connectors/sinks/mqtt
RedisSink data from Kafka to Redis.Connectors -- Redis.pngredis
## FAQ ### Can the datalakes sinks lose data? Kafka topic retention policies determine how long a message is retained in a topic before it is deleted. If the retention period expires and the connector has not processed the messages, possibly due to not running or other issues, the unprocessed Kafka data will be deleted as per the retention policy. This can lead to significant data loss since the messages will no longer be available for the connector to sink to the target system. ### Do the datalake sinks support exactly once semantics? Yes, the datalakes connectors natively support exactly-once guarantees. ### How do I escape dots in field names in KCQL? Field names in Kafka message headers or values may contain dots (`.`). To access these correctly, enclose the entire target in backticks (\`\`\`) and each segment which consists of a field name in single quotes (`'`): ```sql INSERT INTO `_value.'customer.name'.'first.name'` SELECT * FROM topicA ``` ### How do I escape other special characters in field names in KCQL? For field names with spaces or special characters, use a similar escaping strategy: * Field name with a space: `` `_value.'full name'` `` * Field name with special characters: `` `_value.'$special_characters!'` `` This ensures the connector correctly extracts the intended fields and avoids parsing errors. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lenses.io/latest/connectors/kafka-connectors/sinks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.