Re: Lucene syntax query matched against a string content

2008-02-11 Thread Nilesh Bansal
Excellent. MemoryIndex solves the problem. I didn't knew about this index. Thanks. -Nilesh On Feb 8, 2008 8:23 AM, Erick Erickson <[EMAIL PROTECTED]> wrote: > You might want to check out MemoryIndex before rejecting putting a single > doc in memory and searching against it. It's quite fast, altho

Re: Lucene syntax query matched against a string content

2008-02-08 Thread Erick Erickson
You might want to check out MemoryIndex before rejecting putting a single doc in memory and searching against it. It's quite fast, although whether it'll work in your situation only measurement will tell. It's in contrib as I remember. Erick On Feb 7, 2008 11:48 PM, Nilesh Bansal <[EMAIL PROTECTE

Re: Lucene syntax query matched against a string content

2008-02-08 Thread Paul Elschot
Without using a RAMDirectory index it would be necessary to implement all Scorers used by the query directly top of the token stream that normally goes into the index. This is possible, but Lucene is not designed to do this, so it won't be easy. But especially for more preparsed queries against a

Lucene syntax query matched against a string content

2008-02-07 Thread Nilesh Bansal
Hi, I want to create a function, which takes in a query string (in lucene syntax), and a string as content and returns back if the query matches the content or not. This would mean, query = +(apache) +(lucene OR httpd) will match content = HTTPD by Apache foundation is one of the most popular o