Adapt a custom file-only processor to the WatcherProcessor the
service runs on. File operations are forwarded unchanged. Its source
operations fail: every notify-queue run returns a failed result with
source_unavailable (the run's issue, as for a failing callback), and
every other source operation throws the API's 503 not_available, so
POST /documents, POST /metadata { source }, POST /render { source }
and POST /reindex { source } answer as before source support existed.
Use it in a custom createDocumentProcessor factory; never wrap a
processor that has source operations of its own (they would be hidden).
Adapt a custom file-only processor to the WatcherProcessor the service runs on. File operations are forwarded unchanged. Its source operations fail: every notify-queue run returns a
failedresult withsource_unavailable(the run's issue, as for a failing callback), and every other source operation throws the API's503 not_available, soPOST /documents,POST /metadata { source },POST /render { source }andPOST /reindex { source }answer as before source support existed. Use it in a customcreateDocumentProcessorfactory; never wrap a processor that has source operations of its own (they would be hidden).