hanahmily opened a new pull request, #1139: URL: https://github.com/apache/skywalking-banyandb/pull/1139
## What Add stream schema coverage for moving a tag between a searchable tag family and a storage-only tag family. The new case verifies both directions: - `searchable` -> `storage-only` - `storage-only` -> `searchable` It also verifies continued writes during schema propagation and query behavior before and after the move. ## Query behavior covered - Before moving from `searchable` to `storage-only`, the moved tag can be queried through the existing inverted index. - After moving to `storage-only`, data remains queryable and the moved tag can still be filtered as a storage-only tag. - Before moving from `storage-only` to `searchable`, the moved tag is returned from the storage-only family and can be used as a query condition. - After moving to `searchable`, newly written data can be queried through the new searchable/indexed tag layout. - Historical rows remain queryable, but values written under the old tag-family layout are not backfilled into the new family projection and appear as `NULL` in that new projection. - Writes using the old layout during the move are accepted and remain queryable after the schema revision is applied. ## Verification Passed: ```bash make generate go test ./test/cases/schema go test ./test/integration/standalone/schema go test ./test/integration/distributed/schema -ginkgo.focus='Schema tag family move' go test ./test/integration/distributed/schema ``` Ralph/pre-push validation: ```bash make pre-push ``` `make pre-push` passed through: - `check-req` - `generate` - `generate-test-cases` - `lint` - `check` Known skipped item: - `vuln-check` stops on existing `GO-2026-*` govulncheck CVE findings from Go stdlib/dependencies. This was explicitly allowed to be skipped for this task. Architect verification: approved after strengthening assertions for in-move rows and storage-only criteria behavior. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
