Here's another thought: if you desperately need complex searches then
you could do a heuristic filtering to narrow down the search: use an
analyzer that does some form of input splitting into terms (removing
excess whitespace or even producing n-grams from the input), then do
the same for the query
Thanks for the input! Seems I should give this another chance using
the hints you all sent me. I'll report back my findings here.
/Mathias
On Mon, Feb 4, 2013 at 7:01 PM, Mathias Dahl wrote:
> Hi,
>
> I have hacked together a small web front end to the Glimpse text
> indexing engine (see http:/
gt; From: Mathias Dahl [mailto:mathias.d...@gmail.com]
> Sent: Tuesday, February 05, 2013 10:26 AM
> To: java-user
> Subject: Re: Lucene vs Glimpse
>
> Jack,
>
> What you say sounds hopeful, but it also sounds like quite some work to
> define/select the correct ana
esulting sequence of terms would match as a
> phrase. It won't be a 100% solution, but it should do reasonably well.
>
> Is there a query that was failing to match reasonably for you?
>
> -- Jack Krupansky
>
> -Original Message- From: Mathias Dahl
> Sent: Monday, F
. It won't be a 100% solution, but it should do reasonably well.
Is there a query that was failing to match reasonably for you?
-- Jack Krupansky
-Original Message-
From: Mathias Dahl
Sent: Monday, February 04, 2013 1:01 PM
To: java-user@lucene.apache.org
Subject: Lucene vs Glimps
Hi,
I have hacked together a small web front end to the Glimpse text
indexing engine (see http://webglimpse.net/ for information). I am
very happy with how Glimpse indexes and searches data. If I understand
it correctly it uses a combination of an index and searching directly
in the files themselv
