Is your feature request related to a problem? Please describe.
Step two in abstracting the Osprey codebase away from assuming Druid downstream. Follow-up to #188.
What solution would you like?
Finish the decoupling work so the neutral interface is the only path to the analytics database.
Key changes expected:
- Extract the Druid read path into a first-class backend plugin registered through the same hookspec as any other backend
- Migrate the bulk-label path off Druid-specific query objects and onto the neutral backend interface
- Check and complete all migrations (validators, UDFs etc) so no shared type parameterizes on a Druid-shaped model
- Move the Druid client library to an optional install extra so ClickHouse-only deployments don't pull it in
Describe alternatives you have considered
Treat Druid as a "privileged" backend. Rejected — leaves the system unable to actually retire Druid and defeats the goal of #188.
Do you have any additional context?
This is prerequisite work for Step 3
Is your feature request related to a problem? Please describe.
Step two in abstracting the Osprey codebase away from assuming Druid downstream. Follow-up to #188.
What solution would you like?
Finish the decoupling work so the neutral interface is the only path to the analytics database.
Key changes expected:
Describe alternatives you have considered
Treat Druid as a "privileged" backend. Rejected — leaves the system unable to actually retire Druid and defeats the goal of #188.
Do you have any additional context?
This is prerequisite work for Step 3