Porter stemmer is not only agressive, it is ugly, too. The generated
code is too old, too few object centric and should be too slow.
If your kstem compile with java 1.4, why don't you suggest it to lucene
core?
M.
Wagner,Harry a écrit :
Hi HH,
Here's a note I sent Solr-dev a while back:
---
hi,
I have a question ... I need to be able to filter a search using a
regex. I
cannot used facet as the filtering is pretty complex (but easy to
perform
using a regex).
For instance I have stored in the field ID the value 12G and I want to
basically filter out all the results that are > 12
Sushan Rungta a écrit :
Hello Everybody,
I am a newbie in Lucene and I am from India, currently working for a
search module for our classifed website search module in
clickindia.com. I have implemented the basic functionality of solr
lucen and am pretty happy with the results.
Search in Ind
1) document boost is periodicaly recomputed with age as a factor (or
log(age)). It should be slow.
2) Use your own Similarity implementation. Use the DefaultSimilarity
with a dynamic document boost. The Map document id -> age or document id
-> date should be cached with Map, ehCache, whirlcache,
- browsing through the web came I accross an application called the Lucene
Web Service : what do you think of it ? (its goal seems precisely to query
multiple indices, it thus would be the thing I'm searching for ; but
considering the scale of this project, I think I'd prefer to base my work on
