Actually, just realised a PhraseQuery is incorrect...
I only want a single TermQuery but it just needs to be quoted, d'oh.
-Original Message-
Then I found that because that analyser always returns a single token
(TermQuery) it would send through spaces into the final query string,
causing
Hi again,
Thanks for everyone who replied. The PerFieldAnalyzerWrapper was a good
suggestion, and one I had overlooked, but for our particular
requirements it wouldn't quite work so I went with overriding
getFieldQuery().
You were right, Paul. In 1.4.2 a whole heap of QueryParser changes were
m
On Nov 22, 2004, at 9:17 AM, Morus Walter wrote:
Erik Hatcher writes:
If your query isn't entered by users, you shouldn't use query parser
in
most cases anyway.
I'd go even further and say in all cases.
If you use lucene as a search server you have to provide the query
somehow.
E.g. we have an ph
Erik Hatcher writes:
> > If your query isn't entered by users, you shouldn't use query parser in
> > most cases anyway.
>
> I'd go even further and say in all cases.
>
If you use lucene as a search server you have to provide the query somehow.
E.g. we have an php application, that sends queries
On Nov 22, 2004, at 2:56 AM, Morus Walter wrote:
Kauler, Leto S writes:
Would anyone have any suggestions on how this could be done? I was
thinking maybe the QueryParser would have to be changed/extended to
accept a separator other than colon ":", something like "=" for
example
to indicate this c
Kauler, Leto S writes:
>
> Would anyone have any suggestions on how this could be done? I was
> thinking maybe the QueryParser would have to be changed/extended to
> accept a separator other than colon ":", something like "=" for example
> to indicate this clause is not to be tokenised.
I sugg
On Monday 22 November 2004 05:02, Kauler, Leto S wrote:
> Hi Lucene list,
>
> We have the need for analysed and 'not analysed/not tokenised' clauses
> within one query. Imagine an unparsed query like:
>
> +title:"Hello World" +path:Resources\Live\1
>
> In the above example we would want the fir
Hi Lucene list,
We have the need for analysed and 'not analysed/not tokenised' clauses
within one query. Imagine an unparsed query like:
+title:"Hello World" +path:Resources\Live\1
In the above example we would want the first clause to use
StandardAnalyser and the second to use an analyser whic
