lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley" <ysee...@gmail.com>
Subject Re: Query.extractTerms - a poor introspection API?
Date Thu, 06 Apr 2006 16:53:02 GMT
On 4/6/06, mark harwood <markharw00d@yahoo.co.uk> wrote:
> Maybe we should have as a standard part of Query:
>
>   //immediate child queries only
>   Query [] getNestedQueries();

It's still the case that you often need to know what type of query the
parent is.
For example, a BooleanQuery with mandatory, optional, and prohibited clauses.
Or, as Marvin brings up, phrase queries, etc.

One may not want to worry about terms that don't match when constrants
are applied (like a phrase) to begin with, but you don't want to
implement it in such a way that makes it hard to add later.

IMO, the query hierarchy should be fully self-describable... user code
should be able to walk it and re-create the exact same thing if
desired.


-Yonik
http://incubator.apache.org/solr Solr, The Open Source Lucene Search Server

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message