You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Terry Steichen <te...@net-frame.com> on 2002/11/25 17:53:27 UTC
Slash Problem
I've got a Text field (tokenized, indexed, stored) called 'path' which contains a string in the form of '1102\A3345-12RT.XML'. When I submit a query like "path:1102*" it works fine. But, when I try to be more specific (such as "path:1102\a*" or "path:1102*a*") it fails. I've tried escaping the slash ("path:1102\\a*") but that also fails.
I'm using the StandardAnalyzer and the default QueryParser. Could anyone suggest what's going wrong here?
Regards,
Terry
Re: Slash Problem
Posted by Terry Steichen <te...@net-frame.com>.
I confirmed that I can search properly when I replace all my backslashes
with forward slashes. (I had the terminology reversed in my last message.)
I now have to check if the Windows OS will accept the replacement or if I'll
have to do dynamic conversions when I use the content.
It appears that the '\' escape character isn't working (for me, at least).
Regards,
Terry
----- Original Message -----
From: "Terry Steichen" <te...@net-frame.com>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, November 25, 2002 12:25 PM
Subject: Re: Slash Problem
> Rob,
>
> I presume that means that you used backslashes (in the url) rather than
> forward slashes (in the path). I had planned to test that as a workaround
> and it's good to know that you've already tested that successfully.
>
> But why is this necessary? Why doesn't the escape ('\') allow the use of
a
> backslash?
>
> Regards,
>
> Terry
>
> ----- Original Message -----
> From: "Rob Outar" <ro...@ideorlando.org>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Sent: Monday, November 25, 2002 12:01 PM
> Subject: RE: Slash Problem
>
>
> > I don't know if this helps but I had exact same problem, I then stored
the
> > URI instead of the path, I was then able to search on the URI.
> >
> > Thanks,
> >
> > Rob
> >
> >
> > -----Original Message-----
> > From: Terry Steichen [mailto:terry@net-frame.com]
> > Sent: Monday, November 25, 2002 11:53 AM
> > To: Lucene Users Group
> > Subject: Slash Problem
> >
> >
> > I've got a Text field (tokenized, indexed, stored) called 'path' which
> > contains a string in the form of '1102\A3345-12RT.XML'. When I submit a
> > query like "path:1102*" it works fine. But, when I try to be more
> specific
> > (such as "path:1102\a*" or "path:1102*a*") it fails. I've tried
escaping
> > the slash ("path:1102\\a*") but that also fails.
> >
> > I'm using the StandardAnalyzer and the default QueryParser. Could
anyone
> > suggest what's going wrong here?
> >
> > Regards,
> >
> > Terry
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Slash Problem
Posted by Terry Steichen <te...@net-frame.com>.
Rob,
I presume that means that you used backslashes (in the url) rather than
forward slashes (in the path). I had planned to test that as a workaround
and it's good to know that you've already tested that successfully.
But why is this necessary? Why doesn't the escape ('\') allow the use of a
backslash?
Regards,
Terry
----- Original Message -----
From: "Rob Outar" <ro...@ideorlando.org>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, November 25, 2002 12:01 PM
Subject: RE: Slash Problem
> I don't know if this helps but I had exact same problem, I then stored the
> URI instead of the path, I was then able to search on the URI.
>
> Thanks,
>
> Rob
>
>
> -----Original Message-----
> From: Terry Steichen [mailto:terry@net-frame.com]
> Sent: Monday, November 25, 2002 11:53 AM
> To: Lucene Users Group
> Subject: Slash Problem
>
>
> I've got a Text field (tokenized, indexed, stored) called 'path' which
> contains a string in the form of '1102\A3345-12RT.XML'. When I submit a
> query like "path:1102*" it works fine. But, when I try to be more
specific
> (such as "path:1102\a*" or "path:1102*a*") it fails. I've tried escaping
> the slash ("path:1102\\a*") but that also fails.
>
> I'm using the StandardAnalyzer and the default QueryParser. Could anyone
> suggest what's going wrong here?
>
> Regards,
>
> Terry
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Slash Problem
Posted by Rob Outar <ro...@ideorlando.org>.
I don't know if this helps but I had exact same problem, I then stored the
URI instead of the path, I was then able to search on the URI.
Thanks,
Rob
-----Original Message-----
From: Terry Steichen [mailto:terry@net-frame.com]
Sent: Monday, November 25, 2002 11:53 AM
To: Lucene Users Group
Subject: Slash Problem
I've got a Text field (tokenized, indexed, stored) called 'path' which
contains a string in the form of '1102\A3345-12RT.XML'. When I submit a
query like "path:1102*" it works fine. But, when I try to be more specific
(such as "path:1102\a*" or "path:1102*a*") it fails. I've tried escaping
the slash ("path:1102\\a*") but that also fails.
I'm using the StandardAnalyzer and the default QueryParser. Could anyone
suggest what's going wrong here?
Regards,
Terry
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>