Because your "text" field type is completely broken.

for instance, at indexing time
> lowercasing before using WordDelimiterFilterFactory
means that one of the purposes of WDFF, breaking
tokens up on upper/lower case transitions can't happen.
Which you apparently intend since you have
splitOnCaseChange="1"

> you apply stemming at index time but not query time
(not finding q=acted)

For your query,
> you don't lowercase the input (contents:Sushant
not getting hits).

Please spend some time with the admin/analysis page
to understand the transformations at index time and
query time, that'll clarify a lot.

Best
Erick

On Tue, Sep 24, 2013 at 6:49 AM, Nutan <nutanshinde1...@gmail.com> wrote:
> Why does it happens that for few words it shows output and for few it does
> not?
>
> For example,
> 1)
> q=contents:Sushant
>
> numfound is 0
>
> q=contents:sushant
>
> gives output
>
> 2)
> q=contents:acted
>
> numfound 0
>
> q=contents:well
>
> gives output
>
> This is the document:
> <result name="response" numFound="1" start="0">
>   <doc>
>     <str name="id">13</str>
>     <arr name="author">
>       <str>chetan</str>
>     </arr>
>     <str name="comments">worst book</str>
>     <str name="keywords">solr,lucene</str>
>     <str name="contents">Sushant acted well in kaipoche.</str>
>     <str name="title">3 mistakes</str>
>     <str name="revision_number">0012345654334</str></doc>
> </result>
> </response>
>
> Please do reply.Help will be appreciated.
> Thanks in advance.
>
>
>
> --
> View this message in context: 
> http://lucene.472066.n3.nabble.com/searching-within-documents-tp4090173p4091713.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to