[
https://issues.apache.org/jira/browse/SOLR-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Harris updated SOLR-1856:
-------------------------------
Attachment: SOLR-1856.patch
Initial patch. Notes:
* We allow literal values to override all other Tika/SolrCell stuff, including
1) fields in the Tika metadata object, 2) the Tika content field, and 3) any
"captured content" fields
* Currently literalValuesOverrideOtherValues is always true. This could be
made a config option, but my intuition so far is that it's not worth the
complication.
* Includes an initial unit test
* Interestingly, all the old (and unmodified) unit tests still pass.
> In Solr Cell, literals should override Tika-parsed values
> ---------------------------------------------------------
>
> Key: SOLR-1856
> URL: https://issues.apache.org/jira/browse/SOLR-1856
> Project: Solr
> Issue Type: Improvement
> Components: contrib - Solr Cell (Tika extraction)
> Affects Versions: 1.4
> Reporter: Chris Harris
> Attachments: SOLR-1856.patch
>
>
> I propose that ExtractingRequestHandler / SolrCell literals should take
> precedence over Tika-parsed metadata in all situations, including where
> multiValued="false". (Compare SOLR-1633.)
> My personal motivation is that I have several fields (e.g. "title", "date")
> where my own metadata is much superior to what Tika offers, and I want to
> throw those Tika values away. (I actually wouldn't mind throwing away _all_
> Tika-parsed values, but let's set that aside.) SOLR-1634 is one potential
> approach to this, but the fix here might be simpler.
> I'll attach a patch shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
