replicationConfig.asyncEnabled is being removed in Weaviate v1.38 — drop client-side field

[jeroiraz]

Background

Weaviate is removing the replicationConfig.asyncEnabled field from collection schemas. This is the server-side commit weaviate/weaviate@cef789345e (part of weaviate/weaviate#11214). After it ships, the field will:

• be silently dropped when present in POST /v1/schema request bodies (Go's encoding/json ignores unknown fields)
• not appear in GET /v1/schema response bodies

The post-removal behaviour is governed by the existing global ASYNC_REPLICATION_DISABLED runtime override: for any class with factor > 1, async replication runs by default unless that flag is set.

Impact on weaviate-client (latest: v3.13.0)

Technically safe — no crash. The read path defaults missing fields to false:

https://github.com/weaviate/typescript-client/blob/main/src/collections/config/utils.ts#L485

asyncEnabled: v.asyncEnabled ? v.asyncEnabled : false,

But the value the client reports back is misleading. Every replicationConfig.asyncEnabled returned by collection.config.get() will be false, even when the server is actually running async replication (the new default for any class with factor > 1).

The write path (src/collections/configure/index.ts L189, L195, L201, L315, L321) still sends asyncEnabled to the server. The server silently drops it, so user intent is lost without any indication.

Recommended change

1. Remove asyncEnabled from the read-side ReplicationConfig type at src/collections/config/types/index.ts:77.
2. Drop the default-to-false branch in src/collections/config/utils.ts:485.
3. Remove asyncEnabled from the write-side configure options in src/collections/configure/index.ts (the parameter, the JSDoc, and the merge into the outgoing payload at L189–321).

The server change is backward compatible at the wire level (existing classes with asyncEnabled persisted in their schemas are read fine — the field is dropped, not validated). So clients that don't ship the change still work; they just report a misleading false.

Target server version

Weaviate v1.38 (the release that includes #11214).

cc @weaviate/typescript-client-maintainers

[jeroiraz]

Update: the server-side change in #11214 now ships with a compat shim that keeps emitting asyncEnabled in every ReplicationConfig JSON response, derived from factor > 1 AND !ASYNC_REPLICATION_DISABLED. So this client will not see a missing key against a v1.38 server — the value still appears, it's just no longer settable by the user (writes are silently dropped server-side).

The recommended client change is therefore deprecation, not urgent removal: the field is now derived rather than user-controlled, and the long-term plan is to drop it from responses too once SDKs stop expecting it. Take the original recommendation as a deprecation roadmap rather than a compat-break.

Server-side reference for the shim:

• https://github.com/weaviate/weaviate/blob/main/entities/models/replication_config_compat.go (custom MarshalJSON + the package-level flag setter)
• The startup wiring lives in adapters/handlers/rest/configure_api.go, hook AsyncReplicationDisabled and an initial models.SetAsyncReplicationGloballyDisabled(...) call after DB creation.