[
https://issues.apache.org/jira/browse/SOLR-7445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Pugh resolved SOLR-7445.
-----------------------------
Resolution: Won't Fix
In Solr 10 we are leveraging either Tika Server (running in it's own seperate
server process) or maybe Tika Pipes (again, running in a seperate JVM).
Please revalidate your issue against Solr 10 with one of those options, and if
it is still present need, happy to work with you on a fix using the new
approach for Tika.
> Solr Cell field default value parameter
> ---------------------------------------
>
> Key: SOLR-7445
> URL: https://issues.apache.org/jira/browse/SOLR-7445
> Project: Solr
> Issue Type: New Feature
> Components: contrib - Solr Cell (Tika extraction)
> Reporter: Jon Scharff
> Priority: Minor
>
> It appears that in previous versions, literal.<fieldname> was used as a
> default value, and a parsed value overrode it. I understand why one might
> want to be able to override tika-parsed values, but I believe there are
> equally valid use cases for providing default values. Defaults could be
> provided with a default.<fieldname> parameter.
> For example, in office documents and pdfs, a modified field is provided.
> However, this is not included in all such files. It would be useful to be
> able to provide the modified date from the file system to be used only in
> cases where the date is not in the metadata of the file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
