The admin/analysis page is your friend. Taking some time to get acquainted with that page will save you lots and lots and lots of time. In this case, you'd have seen that your input is actually tokenized as (1999/99), parentheses and all as a _single_ token, so of course searching for 1999/99 wouldn't work.
Searching for *1999/99* is generally a bad idea. It'll work, but it's a kludge. What you _do_ need to do is define your use-cases. Let's assume that you _never_ want parentheses to be relevant. You could use PatternReplaceCharFilterFactory or PatternReplaceFilterFactory in both index and query parts of your analysis chain to remove parens. Or really any kinds of extraneous characters you decided were unimportant. But you need to decide what's "important" and enforce that. Best, Erick On Tue, Feb 25, 2014 at 7:28 PM, Kashish <itzz.me.kash...@gmail.com> wrote: > Hi Ahmet/Erick, > > I tried escaping as well. See no luck. > > The title am looking for is - ARABIAN NIGHTS #01 (1999/99) > > I figured out that if i pass the query as *1999/99* (i.e asterisk not only > at the end but at the beginning as well), It works. > > The problem is the braces. I can change my field type and add > > <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" > generateNumberParts="1" catenateWords="1" catenateNumbers="1" > catenateAll="0" splitOnCaseChange="1" preserveOriginal="1"/> > > But this will show too many results in autocomplete. > > Is there any best way to handle this? Or should i pass asterisk before and > after the query? > > Thanks. > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119678.html > Sent from the Solr - User mailing list archive at Nabble.com. >
