[Testing] Verify deletion of single measure/stream/trace

[hanahmily]

Search before asking

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

Description

• Objective: Verify deletion of a single measure or stream or trace where metadata is removed immediately while underlying data is reclaimed later by merge/TTL.
• Test Scope
  • API/CLI: DELETE /groups/{group}/{type:stream|measure|trace}/{name}.
  • Immediate effects: remove metadata; block new writes and routing.
  • Data lifecycle: existing files remain; background merge/compaction/TTL removes them over time.

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

[OmCheeLin]

I will solve it.

[paultanay]

hi @hanahmily I am actively working on it. I will update the progress here.

[paultanay]

@hanahmily

Before I start, could you please clarify the implementation approach?

1: Directory Structure
should I create seperate directory like this - test\integration\standalone\deletion where I will write the integration tests code ? (e.g. deletion\deletion_measure_test.go, deletion\deletion_stream_test.go, deletion\deletion_suite_test.go)

I noticed this pattern is used for other integration tests (e.g., query/, backup/, inspect/), so I'm assuming this is the right approach?

2. What to Test
validate immediate metadata removal, write blocking after deletion, and schema visibility changes ?

[hanahmily]

1. Directory Structure

Create test cases under test/cases/schema/deletion.go. Set up the standalone test environment under test/integration/standalone/schema/deletion.go and the cluster test environment under test/integration/distributed/schema/deletion.go. The test environments should reference the shared test cases.

2. Test Process

2.1 Write several records to the target subject (measure/stream/trace).
2.2 Delete the target subject.
2.3 Verify that new data to the deleted subject is rejected and that the subject is no longer visible.
2.4 Write 20 batches of data to another subject (not the deleted one) in the same group as the deleted subject.
2.5 Verify that all written data can be retrieved successfully. This confirms that data without an associated subject does not affect merge and query operations, since subjects in the same group share the same physical files.

[paultanay]

Hi @hanahmily,

I've completed the implementation following your architectural guidance.

Implementation:

• Shared test cases in test/cases/schema/deletion.go
• Standalone integration tests in test/integration/standalone/schema/deletion.go
• All 3 subjects covered (measure/stream/trace)
• Full 5-step validation process implemented

I've submitted PR apache/skywalking-banyandb#968 for your review.

Note: This PR includes standalone mode tests. I plan to add distributed mode tests in a follow-up PR to keep changes focused and reviewable.

Thanks for your guidance!