AHA! I am using the Search tab and have enteres the query : location:Z:\install\logs\archive.log.D20060406.T141958
the query details says the query was parsed to location:z so if I escape the colon I see the new parsed query as location:"z installlogsarchive.log.d20060406.t141958" So, lucence does not store the file path exactly?! It converts it all lower case! Is there some property I should turn on? Plus, it is not storing the backslash. Should I be escaping these in the index before storing them? It seems so. -Bill On 4/14/06, Bill Snyder <[EMAIL PROTECTED]> wrote: > > Oh, cool. Look at that. A neat tool made with thinlets. I had not heard of > this...I'll see if it helps me figure out whats going on. > > --Bill > > > On 4/14/06, Rajesh Munavalli <[EMAIL PROTECTED]> wrote: > > > > It would be helpful to download Luke (http://www.getopt.org/luke/) and > > analyze whats getting indexed. Have you tried that? > > > > On 4/14/06, Bill Snyder < [EMAIL PROTECTED]> wrote: > > > > > > Hello, > > > > > > We am using Lucene to facilitate searching of our applications log > > files. > > > I > > > am noticing some inconsistencies in result sets when searching on > > certain > > > fields. > > > > > > One field we index is the file path. I am using a simple query like > > > "location:Z:\logs\someLogFile.log". However, I can never get path > > searches > > > like this to come back with any results. Tried escaping the > > backslashes > > > and > > > colon. Nothing seems to work. I missing something here in my syntax? > > > > > > We also index the file name. However, on file names that have mixed > > case > > > or > > > multiple extensions (logfile.D20060303.T234234 ) I cannot get results > > > either. > > > Weird. > > > > > > I haven't worked with Lucene very long, so I expect I am missing > > something > > > simple here. > > > > > > If you need more info, let me know! > > > Many Thanks! > > > > > > --Bill > > > > > > > > > > >
