Feature request · Integrations · Blocks work
Add a registered StarRocks destination connector
1 source thread · first seen 2026-09
Summary
The user proposes an in-repository StarRocks destination because there is no registry entry or Airbyte Cloud path, and self-managed users must build and host a custom image and edit the configuration database. The post asks maintainers whether a Kotlin connector would be accepted.
- Affects
- Self-managed Airbyte users and Airbyte Cloud users
- Workaround
- Build and host a custom Docker connector; self-managed users also hand-edit the Airbyte config database to enable refreshes.
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Today the only way to run Airbyte → StarRocks is a **custom Docker connector**”