This is an automated email from the ASF dual-hosted git repository.
tballison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tika.git
The following commit(s) were added to refs/heads/main by this push:
new 5486c9a2b7 TIKA-4930: document that gRPC component management needs a
shared config store (#3251)
5486c9a2b7 is described below
commit 5486c9a2b75bb7354cfa2b66dcfd2a90fc6bb5ff
Author: Tim Allison <[email protected]>
AuthorDate: Tue Oct 6 13:34:00 2026 -0400
TIKA-4930: document that gRPC component management needs a shared config
store (#3251)
---
docs/modules/ROOT/pages/using-tika/grpc/index.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/docs/modules/ROOT/pages/using-tika/grpc/index.adoc
b/docs/modules/ROOT/pages/using-tika/grpc/index.adoc
index 0e9b7a7135..e088ab5bf2 100644
--- a/docs/modules/ROOT/pages/using-tika/grpc/index.adoc
+++ b/docs/modules/ROOT/pages/using-tika/grpc/index.adoc
@@ -123,6 +123,13 @@ contain passwords, access keys and tokens. When `false`,
the mutating RPCs are r
config.
|===
+Fetches run in the forked pipes workers, and each worker builds its own config
store from the
+same settings. With the default in-memory `configStoreType`, a fetcher saved
through
+`SaveFetcher` exists only in the gRPC JVM and every `FetchAndParse` that names
it fails with
+`FETCHER_NOT_FOUND`. When `allowComponentManagement` is `true`, set
`configStoreType` to `file`
+or `ignite` (see
xref:pipes/configuration.adoc#_distributed_config_store[Distributed Config
+Store]) so the workers see the same store.
+
Enable these only for trusted callers over a secured channel:
[source,json]
