[
https://issues.apache.org/jira/browse/SOLR-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800850#comment-13800850
]
Simon Endele commented on SOLR-1856:
------------------------------------
Debugging the code (Solr 4.4.0) I found out that the parameter "lowernames" is
not considered.
The request "lowernames=true&literalsOverride=true&literal.url=myurl" still
raises an org.apache.solr.common.SolrException: "ERROR: multiple values
encountered for non multiValued field url: [.., ..]", if a URL is extracted
from the metadata of the binary.
> 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)
> Reporter: Chris Harris
> Assignee: Jan Høydahl
> Fix For: 4.0-BETA, 5.0
>
> Attachments: SOLR-1856.patch, SOLR-1856.patch
>
>
> I propose that ExtractingRequestHandler / SolrCell literals should take
> precedence over Tika-parsed metadata in all situations, including where
> multiValued="true". (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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
