[
https://issues.apache.org/jira/browse/SOLR-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938006#comment-13938006
]
Nicholas Jakobsen commented on SOLR-1387:
-----------------------------------------
[~kaukas], we had the same problems as you describe, can't show users downcased
results, "prefix" must match any word, not just anchored at the beginning of
the token. What we ended up doing is encoding more information in the tokenized
values than just the result. We included the downcased search term and the term
to display, but delimited them with a tab, e.g. "star wars Star Wars". Then in
our app we grabbed the last half and showed it to the user. As for getting a
matching prefix on different words, e.g. "wars", we created multiple tokens
where we chomped a word off each time. e.g. "star wars Star Wars", "wars
Star Wars". Each has the same "display portion", but we now have full
control over the "matching portion".
> Add more search options for filtering field facets.
> ---------------------------------------------------
>
> Key: SOLR-1387
> URL: https://issues.apache.org/jira/browse/SOLR-1387
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Anil Khadka
> Fix For: 4.8
>
>
> Currently for filtering the facets, we have to use prefix (which use
> String.startsWith() in java).
> We can add some parameters like
> * facet.iPrefix : this would act like case-insensitive search. (or --->
> facet.prefix=a&facet.caseinsense=on)
> * facet.regex : this is pure regular expression search (which obviously would
> be expensive if issued).
> Moreover, allowing multiple filtering for same field would be great like
> facet.prefix=a OR facet.prefix=A ... sth like this.
> All above concepts could be equally applicable to TermsComponent.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
