I badly need some help on this one. Someone please give some direction.
Regards
Amitesh
--
Sent from: https://lucene.472066.n3.nabble.com/Lucene-Java-Users-f532864.html
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.a
Hi Gus, Thank you your reply!
In my search system; users are complaining that they get results with
negation terms when don't expect. As explained in my original post. User
don't want to get documents having a term like "Non Vitamin K" when they
search for "Vitamin K".
But because each terms ar
Thank you Michael!
I solved this requirement by setting the tokenStream at the field level and
not leaving it to the analyzer. This gives control over altering the full
text before tokenization using custom methods.
This has memory overhead which is handled by writing the documents one at a
time
//Method to create document
private static Document createDocumentTextField(HashMap
fields) {
Document document = new Document();
for (String key : fields.keySet()) {
String val = fields.get(key);
Field f = new TextField(key, val, Field.Store.YES);
During this change I had to change the way I store indexes. This change
results in too many .cfs and .fdt files generated against earlier.
Previously there were 5-7 files in index folder, now it has grown to 40+.
Does it affect having change in the way how indexes are stored internally
with this ch