What you mean is just disabling *stemming* in query phrase? If so, you
can just specify different analysis behavior for query and index. In
your *FieldType* configuration.
If you just want to *partially* disable stemming, like some query do
stemming, some dont. I recommend you to do pre-processing
Hi,
Can i do like.. stemmed match should score a lower then non-stemmed (exact
word) match ?
Thanks
Meghana
--
View this message in context:
http://lucene.472066.n3.nabble.com/disable-stemming-on-query-parser-tp3591420p3631826.html
Sent from the Solr - User mailing list archive at Nabble.com.
Why do you think you require compression? It doesn't affect search.
It should lengthen the document load time. You haven't told us how
big your index is yet, so we can't judge a thing about whether you
really need this or not. You haven't told us what your evidence is that
the index size increases.
Hi,
So we need to find that solr patch , which do add special character on word
, which i index. i like to add here, that the my copy field is multivalued
field, with many sentences. so do it add special character at each word of
that?
and for compression, Erik yes, i am storing my copy field (s
Hi,
So we need to find that solr patch , which do add special character on word
, which i index. i like to add here, that the my copy field is multivalued
field, with many sentences. so do it add special character at each word of
that?
and for compression, Erik yes, i am storing my copy field (s
Actually, 1M records isn't all that much for a Solr index, so I'd
simply test with the
copyfield alternative as it's much easier.
About compression: this simply compresses the *stored* data, which has
essentially no effect on index search speed, but will affect the size of
the file (*.fdt) that co
Hi Dmitry ,
If we add some unseen character sequence to array , doesn't it remove my
stemming at all time? how we can manage stemmed and unstemmed words in the
same field? i am a bit confused on this.
also i tried with making compression on a field, which i use for copy field,
what i read about
The thing is that, if you use stemming you would prefer using it both on
index and query phases. So once you have stemmed your data in the index
phase, changing query parser not to stem wouldn't help, right?
In our company we did so that before stemming a word we would append some
unseen character
Thanks Dmitry for your reply...
i tried this out... it is working fine, but still we are in search of any
less costly solution , if there's any. bcoz if i use copy field, it almost
doubles my index file size.
I don't know if it can be applicable or not , but i am thinking of to make a
query par
You can disable stemming in a copy field. So you need to define one field
with your input data on which stemming will be done and the other field
(copy field), on which stemming will not be done. Then on the client you
can decide which field to search against.
Dmitry
On Fri, Dec 16, 2011 at 2:00
10 matches
Mail list logo
