[ 
https://issues.apache.org/jira/browse/SOLR-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185307#comment-13185307
 ] 

Nicholas Jakobsen commented on SOLR-1387:
-----------------------------------------

I like the idea, as I haven't found any solutions to this problem that are 
compatible with Sunspot (ruby solr interface). Just looking at your code, you 
may want to move some of the loop invariant stuff out of the loops. e.g. the 
downcasing of prefixes is the same every iteration, but you downcase it each 
time through. Same goes for term.uppercase, you could move it out one loop as 
it doesn't change within the prefix loop. 
                
> 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: 3.6, 4.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to