@@ -55,28 +55,16 @@ Storage is configured in `StackConfig.storage` via `StorageConfig`. The `stores`
5555
5656See ` datatypes.py ` for all config types and ` StorageBackendType ` for the enum of supported backends.
5757
58- ### Optional Stores (null to disable)
59-
60- Some store references are optional: setting the reference to ` null ` (not omitting
61- it) means OGX does not construct the store at all, and the API that depends on
62- it degrades gracefully. This is an explicit operator choice made in a run config;
63- the default for every optional reference remains an enabled reference (except
64- ` responses ` , which defaults to ` None ` ), so existing deployments are unaffected
65- unless they opt in.
66-
67- - ** ` inference ` ** -- when ` null ` , no ` InferenceStore ` is constructed: no
68- ` inference_store ` table is created and no background write workers run. Chat
69- completions still work (streaming and non-streaming); the chat completion
70- history endpoints (` list ` , ` retrieve ` , ` messages ` ) report that persistence is
71- not configured (HTTP 501) rather than returning an empty list or a 404.
72- - ** ` responses ` ** -- the ` responses ` reference is nullable in the config schema
73- (` default=None ` ) and ` null ` passes validation, but unlike ` inference ` it is not
74- a runtime toggle: the built-in responses provider always constructs and
75- initializes its store from its own ` persistence.responses ` (a required,
76- non-nullable reference), and the shared ` storage.stores.responses ` reference
77- is only validated, never consumed at startup. Setting it to ` null ` is accepted
78- but does not currently disable Responses persistence.
79-
80- Other stores (` datasets ` , ` eval ` , ` files ` , ` prompts ` , ` vector_io ` ) are not
81- affected by disabling the inference store, so persistence can be turned off for
82- one API independently of the rest of the storage layer.
58+ ### Inference Store (null to disable)
59+
60+ Setting the ` inference ` store reference to ` null ` explicitly disables Chat
61+ Completions persistence. Omitting the reference keeps the store enabled for
62+ backward compatibility.
63+
64+ When disabled, no ` InferenceStore ` is constructed, no ` inference_store ` table is
65+ created, and no background write workers run. Streaming and non-streaming Chat
66+ Completions continue to work. The history endpoints (` list ` , ` retrieve ` , and
67+ ` messages ` ) report that persistence is not configured (HTTP 501).
68+
69+ Other stores (` responses ` , ` datasets ` , ` eval ` , ` files ` , ` prompts ` , ` vector_io ` )
70+ are unaffected by disabling the inference store.
0 commit comments