Fix wrong banyanDB resource options in record data

[mrproliu]

What's the problem

In MetadataRegistry.parseMetadata, the RECORDS stream-group branch builds its
SchemaMetadata from config.getRecordsBrowserErrorLog() instead of
config.getRecordsNormal():

case RECORDS:
    return new SchemaMetadata(
        namespace,
        BanyanDB.StreamGroup.RECORDS.getName(),   // group = sw_records
        model.getName(),
        Kind.STREAM,
        model.getDownsampling(),
        config.getRecordsBrowserErrorLog()         // <-- wrong: should be recordsNormal
    );

As a result the sw_records group is created/reconciled with the
recordsBrowserErrorLog settings (its shardNum, segmentInterval, ttl,
per-stage warm/cold config) rather than its own records settings. The
RECORDS_LOG and RECORDS_BROWSER_ERROR_LOG branches are already correct; only
RECORDS is affected.

Why it matters

BanyanDBIndexInstaller reconciles a group on startup (init mode) by comparing
every field — including per-stage shardNum / segmentInterval / ttl — and
issues client.update on drift. Because sw_records was being fed the wrong
config object, its group settings silently tracked
SW_STORAGE_BANYANDB_BROWSER_ERROR_LOG_* instead of
SW_STORAGE_BANYANDB_RECORDS_*. In deployments where the two differ (e.g. a
different shardNum), this can drive sw_records to the wrong shard count or
segment-interval grid.

The fix

Point the RECORDS branch at the correct config getter:

config.getRecordsNormal()

One-line change. getRecordsNormal() is the existing Lombok getter for the
recordsNormal field, populated from the records section of bydb.yml
(SW_STORAGE_BANYANDB_RECORDS_*).

Impact

• sw_records now honors its own records configuration.

• The RECORDS_LOG / RECORDS_BROWSER_ERROR_LOG groups are untouched.

• Segment-interval changes only affect newly created segments; existing segments
  keep their grid and no data is rewritten or lost.

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.

• Update the CHANGES log.

[Copilot]

Pull request overview

Fixes BanyanDB schema metadata construction for the RECORDS stream-group so the sw_records group is reconciled/created using the intended records (recordsNormal) configuration, not the browser error log configuration. Also updates the changelog to record the fix.

Changes:

• Update MetadataRegistry.parseMetadata to use config.getRecordsNormal() for StreamGroup.RECORDS.
• Add a corresponding entry to docs/en/changes/changes.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
oap-server/server-storage-plugin/storage-banyandb-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/banyandb/MetadataRegistry.java	Fixes RECORDS stream-group schema metadata to use the correct BanyanDB group resource config (recordsNormal).
docs/en/changes/changes.md	Documents the BanyanDB records resource-option fix in the changelog.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.