Re: Starts With x and Ends With x Queries

2005-02-08 Thread sergiu gordea
Hi Erik, I'm not changing any functionality. WildcardQuery will still support leading wildcard characters, QueryParser will still disallow them. All I'm going to change is the javadoc that makes it sound like WildcardQuery does not support leading wildcard characters. Erik From what I

Re: Starts With x and Ends With x Queries

2005-02-08 Thread Erik Hatcher
On Feb 8, 2005, at 10:37 AM, sergiu gordea wrote: Hi Erik, I'm not changing any functionality. WildcardQuery will still support leading wildcard characters, QueryParser will still disallow them. All I'm going to change is the javadoc that makes it sound like WildcardQuery does not support

RE: Starts With x and Ends With x Queries

2005-02-08 Thread Chong, Herb
commercial text analytics tools including search engines usually tokenize with splitting of compound words for German. Herb -Original Message- From: sergiu gordea [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 08, 2005 10:38 AM To: Lucene Users List Subject: Re: Starts With x

Re: Starts With x and Ends With x Queries

2005-02-08 Thread sergiu gordea
Chong, Herb wrote: commercial text analytics tools including search engines usually tokenize with splitting of compound words for German. Herb That might be true ... but our application is not a text analysis aplication, and it is also not intended to be a search engine. We use lucene just to

Re: Starts With x and Ends With x Queries

2005-02-08 Thread sergiu gordea
Erik Hatcher wrote: On Feb 8, 2005, at 10:37 AM, sergiu gordea wrote: Hi Erik, I'm not changing any functionality. WildcardQuery will still support leading wildcard characters, QueryParser will still disallow them. All I'm going to change is the javadoc that makes it sound like WildcardQuery

RE: Starts With x and Ends With x Queries

2005-02-08 Thread Chong, Herb
i would say that matching root words in German compounds is a text analysis application. Herb... -Original Message- From: sergiu gordea [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 08, 2005 11:08 AM To: Lucene Users List Subject: Re: Starts With x and Ends With x Queries That

Re: Starts With x and Ends With x Queries

2005-02-07 Thread Erik Hatcher
On Feb 7, 2005, at 2:07 AM, sergiu gordea wrote: Hi Erick, In order to prevent extremely slow WildcardQueries, a Wildcard term must not start with one of the wildcards code*/code or code?/code. I don't read that as saying you cannot use an initial wildcard character, but rather as if you use

Re: Starts With x and Ends With x Queries

2005-02-07 Thread Luke Shannon
I implemented this concept for my ends with query. It works very well! - Original Message - From: Chris Hostetter [EMAIL PROTECTED] To: Lucene Users List lucene-user@jakarta.apache.org Sent: Friday, February 04, 2005 9:37 PM Subject: Re: Starts With x and Ends With x Queries : Also

Re: Starts With x and Ends With x Queries

2005-02-06 Thread Erik Hatcher
On Feb 4, 2005, at 9:37 PM, Chris Hostetter wrote: If you want to start doing suffix queries (ie: all names ending with s, or all names ending with Smith) one approach would be to use WildcarQuery, which as Erik mentioned, will allow you to use a quey Term that starts with a *. ie... Query q3

Re: Starts With x and Ends With x Queries

2005-02-06 Thread Chris Hostetter
: book Managing Gigabytes, making *string* queries drastically more : efficient for searching (though also impacting index size). Take the : term cat. It would be indexed with all rotated variations with an : end of word marker added: ... : The query for *at* would be preprocessed and

Re: Starts With x and Ends With x Queries

2005-02-06 Thread sergiu gordea
Hi Erick, In order to prevent extremely slow WildcardQueries, a Wildcard term must not start with one of the wildcards code*/code or code?/code. I don't read that as saying you cannot use an initial wildcard character, but rather as if you use a leading wildcard character you risk

Starts With x and Ends With x Queries

2005-02-04 Thread Luke Shannon
Hello; I have these two documents: Textsort:9 Keywordmodified:0e1as4og8 Textprogress_ref:1099927045180 Textname:FutureBrand Testing Textdesc:Demo Textanouncement:We are testing our project Textcategory:Category 1 Textolfaithfull:stillhere Textposter:hello Texturgent:yes Textprovider:Mo

Re: Starts With x and Ends With x Queries

2005-02-04 Thread Erik Hatcher
It matches both because you're tokenizing the name field. In both documents, the name field has a testing term in it (it gets lowercased also). A PrefixQuery matches terms that start with the prefix. Use an untokenized field type (Field.Keyword) if you want to keep the entire original

Re: Starts With x and Ends With x Queries

2005-02-04 Thread Chris Hostetter
: Also keep in mind that QueryParser only allows a trailing asterisk, : creating a PrefixQuery. However, if you use a WildcardQuery directly, : you can use an asterisk as the starting character (at the risk of : performance). On the issue of ends with wildcard queries, I wanted to throw out and

Re: Starts With x and Ends With x Queries

2005-02-04 Thread Peter Pimley
Well done. I was so annoyed with the humiliation-for-kicks this afternoon that I just practised my self-destruction technicques with some friends this evening ;) As for configuration, java.lang.system.getenv will give you access to an environment variable.

Re: Starts With x and Ends With x Queries

2005-02-04 Thread Peter Pimley
I sent this to the wrong address. Sorry. Peter Pimley wrote: Well done. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]