tballison commented on code in PR #4853:
URL: https://github.com/apache/solr/pull/4853#discussion_r3937569191


##########
solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-tika.adoc:
##########
@@ -540,9 +552,33 @@ So you can use the other URPs without worrying about 
unexpected field additions.
 
 === Parser-Specific Properties
 
-Parser-specific properties for Tika must be configured directly on your Tika 
Server instance. Consult the https://tika.apache.org/[Apache Tika 
documentation] for details.
+Server-wide parser properties (things that should apply to every request) must 
be configured directly on your Tika Server instance, via its own JSON 
configuration file. Consult the https://tika.apache.org/[Apache Tika 
documentation] for details.
+
+For a single request, you can instead pass parser-specific options through 
Solr using the `tikaserver.config` parameter, whose value is a raw JSON object 
matching Tika Server's per-request configuration format.
+For example, to disable OCR for one request:
+
+[,console]
+----
+$ bin/solr post -c gettingstarted example/exampledocs/solr-word.pdf --params 
'literal.id=doc1&tikaserver.config={"pdf-parser":{"ocr":{"strategy":"NO_OCR"}}}'
+----
+
+[IMPORTANT]
+====
+`tikaserver.config` requires your Tika Server to be started with 
`allowPerRequestConfig: true` in its own JSON configuration (under the `server` 
section).

Review Comment:
   This sentence by itself suggests that you have to have this. I'd recommend 
editing so there's an "if you want per file config, you'll need this". Ignore 
this comment if `tikaserver.config` is saying exactly that. :/



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to