On 4/14/06, Erick Erickson <[EMAIL PROTECTED]> wrote:
>
> Something that took me a while to get was that the analyzer is important
> BOTH in the indexing phase and in the searching phase (assuming you're
> using
> the QueryParser). For you experiment, you probably want to use the
> WhitespaceAnalyz
Something that took me a while to get was that the analyzer is important
BOTH in the indexing phase and in the searching phase (assuming you're using
the QueryParser). For you experiment, you probably want to use the
WhitespaceAnalyzer. See page 119 of "Lucene in Action".
The other three most-comm
oops, thought that you were just referring to the lowercase...
:)
On 4/14/06, karl wettin <[EMAIL PROTECTED]> wrote:
>
>
> 14 apr 2006 kl. 17.22 skrev karl wettin:
> >
> > It is the Analyzer that does that. Try creating your IndexSearcher
> > with a KeywordAnalyzer (it think).
>
> err
>
> It is th
14 apr 2006 kl. 17.22 skrev karl wettin:
It is the Analyzer that does that. Try creating your IndexSearcher
with a KeywordAnalyzer (it think).
err
It is the Analyzer that does that. Try using a KeywordAnalyzer (it
think).
Thanks! OK, how do I get the file separator to be part of the term? Luke
shows the parsed query as ignoring the file separator.
so location:Z\:\\/install/logs\\jetspeedservices.log
becomes location:"z install logs jetspeedservices.log"
--Bill
On 4/14/06, Rajesh Munavalli <[EMAIL PROTECTED]> w
On 4/14/06, Bill Snyder <[EMAIL PROTECTED]> wrote:
>
> 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
14 apr 2006 kl. 17.11 skrev Bill Snyder:
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?
It is the Anal
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, lucenc
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 in
14 apr 2006 kl. 16.37 skrev Bill Snyder:
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.
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 inconsistenc
11 matches
Mail list logo
