janhoy commented on code in PR #4853:
URL: https://github.com/apache/solr/pull/4853#discussion_r3937631359
##########
solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-tika.adoc:
##########
@@ -384,6 +384,18 @@ Example: `passwordsFile=/path/to/passwords.txt`
// +
// Only applicable for `tikaserver` backend. Can only be set in
`solrconfig.xml`, not per request.
+`tikaserver.config`::
++
+[%autowidth,frame=none]
+|===
+|Optional |Default: none
+|===
++
+A raw JSON object sent as the per-request parser configuration for Tika Server
(e.g., `{"pdf-parser":{"ocr":{"strategy":"NO_OCR"}}}`).
+See <<Parser-Specific Properties>> below for details and an important security
note: this requires `allowPerRequestConfig=true` on the Tika Server, which is
off by default.
++
+Example: `tikaserver.config={"pdf-parser":{"ocr":{"strategy":"NO_OCR"}}}`
Review Comment:
What triggered you to enable this? Can we not just tell users to configure
their Tika Server?
I view extraction handler as a low-end solution for folks who have very
simple extraction needs and just want it embedded in solr. If you hare in the
business of really heavy extraction you're probably running a custom Tika
cluster on the application side and inject already extracted text in plain solr
documents?
There is a cost associated with every additional config we need to document,
support, deprecate if tika changes format etc. If you give a real-life example
of its utility, something we believe will be truly useful, then I want to hear.
--
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]
