[
https://issues.apache.org/jira/browse/SOLR-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797273#comment-13797273
]
Jan Høydahl commented on SOLR-1634:
-----------------------------------
Hi,
Can you please open a *new* JIRA issue for the exact problem you are outlining
here, which seems to be a corner case with upper/lowercase between Tika
metadata and literals. Also please give a real world example of where it causes
problems. Real-life issues tend to be prioritized over hypothetical ones.
To me it sounds like a potential, very simple solution would be to apply
lowercasing at several places if {{lowernames=true}}
> change order of field operations in SolrCell
> --------------------------------------------
>
> Key: SOLR-1634
> URL: https://issues.apache.org/jira/browse/SOLR-1634
> Project: Solr
> Issue Type: Improvement
> Components: contrib - Solr Cell (Tika extraction)
> Reporter: Hoss Man
>
> As noted on the mailing list, SolrCell evaluates fmap.* params AFTER
> literal.* params. This makes it impossible for users to map tika produced
> fields to other names (possibly for the purpose of ignoring them completely)
> and then using literal to provide explicit values for those fields. At first
> glance this seems like a bug, except that it is explicitly documented...
> http://wiki.apache.org/solr/ExtractingRequestHandler#Order_of_field_operations
> ...so i'm opening this as an "Improvement". We should either consider
> changing the order of operations, or find some other way to support what
> seems like a very common use case...
> http://old.nabble.com/Re%3A-WELCOME-to-solr-user%40lucene.apache.org-to26650071.html#a26650071
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
