Now you've got it Hossman.
I don't plan on mucking with the parser syntax. I look at this feature as a
smarter default field. Instead of it being one field, it is an array of
them constructed via Dismax with various boosts.
~ David
hossman wrote:
>
>
> : Either I use defType of DISMAX to g
I'm looking at the latest source and I see that the only way I can use
Lucene's DisjunctionMaxQuery is to use the limited query syntax. These two
are entangled together in SolrPluginUtils.DisjunctionMaxQueryParser. Am I
looking at the wrong place? I'd love to be proven wrong.
We want our users
: Either I use defType of DISMAX to get DisjunctionMaxQuery but then I can't
: use prefix queries and more complicated boolean queries, OR I use the
: standard defType which doesn't use DisjunctionMaxQuery.
I think I missunderstood your complaint ... it sounds like you don't care
about (or want)
In 1.3 (trunk, dev build), the query parsing has been extracted into a
component. It shoudl be easy to replace just query parsing component
and keep the rest of the chain the same.
I'm not quite following why it is a problem to have two urls for
dismax vs standard query. Dismax expects un
I'm already aware of defType but that doesn't really change things.
Either I use defType of DISMAX to get DisjunctionMaxQuery but then I can't
use prefix queries and more complicated boolean queries, OR I use the
standard defType which doesn't use DisjunctionMaxQuery.
I need this feature ASAP so
I'm already aware of defType but that doesn't really change things.
Either I use defType of DISMAX to get DisjunctionMaxQuery but then I can't
use prefix queries and more complicated boolean queries, OR I use the
standard defType which doesn't use DisjunctionMaxQuery.
I need this feature ASAP so
: I am frustrated that I have to pick between the two because I want both. The
: way I look at it, there should be a more configurable query handler which
: allows me to dimax if I want to, and pick a parser for the user's query
: (like the flexible one used by the standard query handler, or the
I am frustrated that I have to pick between the two because I want both. The
way I look at it, there should be a more configurable query handler which
allows me to dimax if I want to, and pick a parser for the user's query
(like the flexible one used by the standard query handler, or the more
res
: Is the main difference between the StandardQueryHandler and
: DisMaxQueryHandler the supported query syntax (and different query
: parser used in each of them), and the fact that the latter creates
: DisjunctionMaxQueries, while the former just creates vanilla
: BooleanQueries? Are there any ot
