Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of findmath@gmail.com designates
 64.233.184.238 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=K073BZoT8BbjVNLKX2xLZOZ0JIjBB3XTdpkQcXd66Feg8aEDHS9q0Fi9GeOicrY3nfu2NfDVKWSSfZwLDkaNEgOY3vkxyUGi0/FjOHptTZ8fpFW9iHZVLqoRX2vjLAIWP0Y8Fq5lnHavkVV/mgwJGRgJ5WhFwoU769+OP1N/4b4=
Message-ID: <abe188f20604140819w47197ef7q36be6bb2720413b1@mail.gmail.com>
Date: Fri, 14 Apr 2006 10:19:59 -0500
From: "Rajesh Munavalli" <findmath@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: Syntax help
In-Reply-To: <e465bf5d0604140811j305534e4ye4859d4f7ea8139e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_28266_7717975.1145027999643"
References: <e465bf5d0604140737l26a230c2ga38c4becc6f6631c@mail.gmail.com>
	 <abe188f20604140743m2705a013k5714cc231c23c231@mail.gmail.com>
	 <e465bf5d0604140749y476715a9v3b1c4c64b878b980@mail.gmail.com>
	 <e465bf5d0604140811j305534e4ye4859d4f7ea8139e@mail.gmail.com>

------=_Part_28266_7717975.1145027999643
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 4/14/06, Bill Snyder <wsnyder6@gmail.com> 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
>
> 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?


In the StandardAnalyzer, the LowerCaseFilter converts everything into lower
case. You can skip that step.

Plus, it is not storing the backslash. Should I be escaping these in the
> index before storing them? It seems so.

Yes

-Bill

On 4/14/06, Bill Snyder <wsnyder6@gmail.com> wrote:
>
> Oh, cool. Look at that. A neat tool made with thinlets. I had not heard o=
f
> this...I'll see if it helps me figure out whats going on.
>
> --Bill
>
>
> On 4/14/06, Rajesh Munavalli <findmath@gmail.com> 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 < wsnyder6@gmail.com> 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
> > >
> > >
> >
> >
>

------=_Part_28266_7717975.1145027999643--