[
https://issues.apache.org/jira/browse/SOLR-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492751
]
Hoss Man commented on SOLR-219:
-------------------------------
I'm not opposed to an approach like this ... but it seems like a slippery slope
to go down, with hard coded test strings, and assumptions about how analyzers
will behave in all cases beased on one test case.
perhaps a simpler approach that requires less guess work would be adding the
ability for Fields and FieldTypes to container arbitrary key/val pair options
that can be accessed as a map, and document that SolrQueryParser looks at some
of these to make query parsing decisions?
<fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.WhitespaceTokenizerFactory"/>
</analyzer>
<option name="lowerCaseForPrefix">false</option>
</fieldType>
> Determine if prefix, wildcard, fuzzy queries should be lowercased
> -----------------------------------------------------------------
>
> Key: SOLR-219
> URL: https://issues.apache.org/jira/browse/SOLR-219
> Project: Solr
> Issue Type: Improvement
> Reporter: Yonik Seeley
> Priority: Minor
> Attachments: lowercase_prefix.patch
>
>
> Solr should be able to "do the right thing" when doing prefix/wildcard/fuzzy
> queries on fields with respect to lowercasing or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
