Skip to content

docs(rum): document the HarmonyOS batching configuration - #278

Merged
Fiona2016 merged 1 commit into
mainfrom
docs/harmony-sdk-0.5.0-batching
Aug 19, 2026
Merged

docs(rum): document the HarmonyOS batching configuration#278
Fiona2016 merged 1 commit into
mainfrom
docs/harmony-sdk-0.5.0-batching

Conversation

@Fiona2016

Copy link
Copy Markdown
Contributor

Why

HarmonyOS SDK 0.5.0 replaced setBatchUploadFrequencyMs with the three batching
enums the Android, iOS and Flutter SDKs already use. This page still documented
the removed method in 6 places, across zh and en.

What changed

zh/rum/sdk/harmony/advanced-config.mdx and en/rum/sdk/harmony/advanced-config.mdx:

  • Import block and the configuration sample now use UploadFrequency,
    BatchSize and BatchProcessingLevel.
  • The parameter table replaces one row with three, listing every case and its
    value so readers do not have to look them up in the SDK.
  • The deferred-upload section refers to setUploadFrequency().
  • A note records the migration and the two defaults that moved (upload interval
    5 s → 2 s, batch window 5 s → 10 s), both to match the other platforms.

setBatchProcessingLevel is new in 0.5.0 and had no documentation. It bounds how
many batches go out back-to-back, so the table says when to lower it: an app with
latency-sensitive requests of its own on a narrow uplink.

Verification

No references to the removed method remain outside the migration note itself.

The HarmonyOS SDK expressed upload pacing as a millisecond setter while the
Android, iOS and Flutter SDKs used three enums, so this page taught a vocabulary
readers could not carry to the other platforms. SDK 0.5.0 adopted the shared
enums and removed the millisecond setter, leaving the page documenting a method
that no longer exists.

Replace it with UploadFrequency, BatchSize and BatchProcessingLevel, and record
the two defaults that moved so readers upgrading from 0.4.0 can see them without
diffing the changelog. BatchProcessingLevel is new; the table says what it is
for, since bounding an upload burst is the reason to reach for it.
@Fiona2016
Fiona2016 merged commit aeb8e11 into main Aug 19, 2026
1 check 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