Skip to content

feat: optional driver label to distinguish same-backend variants - #23

Merged
merlimat merged 1 commit into
mainfrom
feat-driver-labels
Jul 2, 2026
Merged

feat: optional driver label to distinguish same-backend variants#23
merlimat merged 1 commit into
mainfrom
feat-driver-labels

Conversation

@merlimat

@merlimat merlimat commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

What

Adds an optional label to driver configs (DriverConfig.label). When present, DriverFactory uses it as the driver's reported name; otherwise the driver's own name is used (no behavior change for existing configs).

Why

The comparison harness runs the same backend under different configurations — e.g. oxia clusters of 3, 6, and 12 nodes. Without a label they all report as oxia and collapse into one series in the aggregated report. With label: oxia-3 / oxia-6 / oxia-12 they stay distinct.

Test

DriverConfigTest covers parsing with and without a label; ./gradlew test green.

Add an optional `label` field to driver configs. When set, DriverFactory
reports it as the driver name in results, so runs of the same backend with
different configurations (e.g. oxia clusters of 3/6/12 nodes) appear as
distinct series (oxia-3, oxia-6, oxia-12) instead of collapsing into one
"oxia". Unset keeps the driver's own name, so existing configs are unchanged.

Signed-off-by: Matteo Merli <mmerli@apache.org>
@merlimat
merlimat merged commit bfb2611 into main Jul 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant