ScyllaDB Agent for Gluesync: Features Overview
Core principles
This agent establishes a connection to ScyllaDB via the official ScyllaDB Java driver.
Supported version
With this agent, you can target any ScyllaDB deployment, whether it is ScyllaDB Cloud, On-prem or hosted under a public cloud provider.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Writes to ScyllaDB via the official Java driver with cluster awareness. |
Source role |
✅ |
Captures CDC streams using ScyllaDB’s CDC tables (see |
Snapshots |
✅ |
Snapshot batches are inserted through the driver before CDC starts. |
CDC |
✅ |
Continuous CDC powered by ScyllaDB’s CDC log tables. |
CDC type |
ScyllaDB CDC tables |
Agent reads CDC table partitions for incremental changes. |
Bulk load |
N/A |
Driver batching already optimizes throughput; no staging workflow. |
Database pooling |
✅ |
Supports connection pooling for efficient resource utilization across multiple pipelines. |
Source persisted internal cache |
N/A |
State tracked in Core Hub metadata and CDC checkpoints. |
Target persisted internal cache |
N/A |
Writes go directly to ScyllaDB via the driver. |
Driver / connector |
ScyllaDB Java driver |
Supports TLS and load-balanced connections. |
Chains |
N/A |
Not supported being a NoSQL database. |
Truncate operation support (reading) |
N/A |
CDC log exposes TRUNCATE events but those are not yet supported. |
Truncate operation support (writing) |
✅ |
Honors Core Hub “TRUNCATE before snapshot” when targeting ScyllaDB. |
