[Feature] Will SkyWalking support Doris in the future?

[dannytest2709-droid]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

Hi all, I have a few questions regarding SkyWalking’s storage support:

Currently, SkyWalking natively supports MySQL, Elasticsearch, H2, etc., but Doris is not listed in the official documentation. Are there any plans to support Doris in the future?

If there are plans, what is the rough timeline for Doris support?

Why is MySQL supported but not Doris? Is it due to architectural compatibility, community priorities, or other reasons?

In multi-cloud, large-scale monitoring scenarios, if we want to use Doris as a backend storage, are there any recommended interim solutions or best practices?

Thanks for any guidance and advice!

Use case

No response

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

Doris and the team came and disappeared. I am not a doris user, and some PMC members are working on BanyanDB as nativr solution.

[wu-sheng]

You could search PR and discussions. A lot happened. But no one made it actually works, including clickhouse.

[Aaron199]

@wu-sheng Thanks for the context. It's a bit unfortunate to hear that the Doris integration discussions faded out — Apache Doris has gained significant traction in the observability space, especially for large-scale log/trace/metrics storage with its high-throughput OLAP capabilities and MySQL-compatible protocol.

Given that SkyWalking already has a MySQL storage plugin, and Doris is wire-compatible with the MySQL protocol, I'm curious — was the prior effort blocked more by architectural mismatches (e.g., batch-insert semantics, schema differences) or simply by lack of sustained contributor bandwidth?

This seems like a valuable integration for the community, especially for teams already running Doris in their data stack. Is there any appetite to revisit this if someone were willing to drive the implementation end-to-end? I'd be interested in understanding what the key technical blockers were so we can evaluate whether it's worth picking up again.

[wu-sheng]

From my end, nothing is blocking them. The key is, Doris community and company behind them lacked of motivations.
We have clear path to add storage support. And they even could do 3rd party release, considering OAP is very stable for storage APIs.