lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: parsing Java log file with Lucene 3.0.3
Date Sun, 02 Jan 2011 02:24:21 GMT
<<<If I'll replace dot with commas it will appear with commas in search

No, that is not the case. Storing a field stores an exact copy of the
input, without any analysis. The intent of storing a field is to return
something to display in the results list that reflects the original
document. What use would it be to store something that had gone
through the analysis chain? Would you really want to show the user
say, the stemmed version of the input text?


On Sat, Jan 1, 2011 at 4:47 PM, Benzion G <> wrote:

> Hi,
> Of course I thought about replacing dots by commas or blanks. But I add
> this
> field as Filed.Store.YES.
> If I'll replace dot with commas it will appear with commas in search
> results.
> I also considered adding it as 2 fields:
> 1. With dots replaced by commas for index and Filed.Store.NO
> 2. The original message with Filed.Store.YES and not indexed.
> But I'm afraid it will make my index files much bigger. Since I'm indexing
> log files the index will be anyway too big so I can't make it even bigger.
> --
> View this message in context:
> Sent from the Lucene - Java Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message