Chris,
On Thu, October 11, 2007, Chris Hostetter wrote:
> ... are you talking about preventing people from including field
> specific queries in their query string? i'm guessing that you mean
> something like this is okay...
>
> solr title:bobby body:boy
>
> ...but this isn't...
>
>
: This would be nice, but unfortunately I do not have direct access
: to the solr server in my application. I need to parse queries,
: filter out blacklisted facettes and then parse them on to solr
: using solrj.
that depends ... what do you mean by a blacklisted facet?
facet counts are controlle
Martin Dietze wrote:
On Wed, October 10, 2007, Mark Miller wrote:
Back in the day you might have been able to call Query.toString() as the
Query contract says that toString() should output valid QueryParser syntax.
This does not work for many queries though (most notably Span Queries --
On Wed, October 10, 2007, Mark Miller wrote:
> Back in the day you might have been able to call Query.toString() as the
> Query contract says that toString() should output valid QueryParser syntax.
> This does not work for many queries though (most notably Span Queries --
> QueryParser knows no
On Wed, October 10, 2007, Chris Hostetter wrote:
> Eh ... not really. it would be easier to just load the Qsol parser in
> solr ... or toString() the query...
This would be nice, but unfortunately I do not have direct access
to the solr server in my application. I need to parse queries,
filter
: As usual, thank you to the gruff but brilliant Mr Hostetter.
Doh! ... sorry if i've been gruffer then usual ... i've been rotating my
sleep schedule so my days start an hour earlier each day for the last 6
days. it's been throwing my psyche for a loop.
-Hoss
--
As usual, thank you to the gruff but brilliant Mr Hostetter.
- Mark
Chris Hostetter wrote:
: I have only taken passing glances at Solr, so I am afraid I cannot be of much
: help. Certainly one of the Solr guys will be able to be of assistance though.
the StandardRequestHandler in solr will acc
: I have only taken passing glances at Solr, so I am afraid I cannot be of much
: help. Certainly one of the Solr guys will be able to be of assistance though.
the StandardRequestHandler in solr will accept anythign the lucene
QueryParser will accept ... sublcassing StandardRequestHandler to us
I have only taken passing glances at Solr, so I am afraid I cannot be of
much help. Certainly one of the Solr guys will be able to be of
assistance though.
Since Qsol generates Query objects, you just need to find out how to
bypass sending solr a query String and instead give it a Query object
Mark,
On Wed, October 10, 2007, Martin Dietze wrote:
> > Qsol: myhardshadow.com/qsol (A query parser I wrote that has fully
> > customizable precedence support - don't be fooled by the stale website...I
> > am actually working on version 2 as i have time)
>
> That sounds promising, I will chec
Mark,
this reply was just in time :)
On Wed, October 10, 2007, Mark Miller wrote:
> Precedence QueryParser (I think its in Lucene contrib packages - I don't
> believe its perfect but I have not tried it)
I checked that one out, and while it improves things with
default settings I found it to
On Tue, October 09, 2007, Daniel Naber wrote:
> The operator precedence is known to be buggy. You need to use parenthesis,
> e.g. (aa AND bb) OR (cc AND dd)
This would be fine with me but unfortunately not for my users.
More precisely, I need to analyze a query string from one search
engine, fil
There is a lot on this topic if you search the archives.
Things to check out:
Precedence QueryParser (I think its in Lucene contrib packages - I don't
believe its perfect but I have not tried it)
Qsol: myhardshadow.com/qsol (A query parser I wrote that has fully
customizable precedence suppo
On Tuesday 09 October 2007 09:55, Martin Dietze wrote:
> I've been going nuts trying to use LuceneParser parse query
> strings using the default operator AND correctly:
The operator precedence is known to be buggy. You need to use parenthesis,
e.g. (aa AND bb) OR (cc AND dd)
regards
Daniel
-
Hi,
I've been going nuts trying to use LuceneParser parse query
strings using the default operator AND correctly:
String queryString = getQueryString();
QueryParser parser = new QueryParser("text", new StandardAnalyzer());
parser.setDefaultOperator(QueryParser.AND_OPERATOR);
try {
Query q = pa
15 matches
Mail list logo