Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Mime-Version: 1.0 (Apple Message framework v746.3)
In-Reply-To: <20060406095213.13703.qmail@web26009.mail.ukl.yahoo.com>
References: <20060406095213.13703.qmail@web26009.mail.ukl.yahoo.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <347865A8-218F-42D1-93A6-306F5A3A544A@rectangular.com>
Content-Transfer-Encoding: 7bit
From: Marvin Humphrey <marvin@rectangular.com>
Subject: Re: Query.extractTerms - a poor introspection API?
Date: Thu, 6 Apr 2006 07:04:50 -0700
To: java-dev@lucene.apache.org


On Apr 6, 2006, at 2:52 AM, mark harwood wrote:
> Maybe we should have as a standard part of Query:
>
>   //immediate child queries only
>   Query [] getNestedQueries();
>
> and...
>   //immediate terms only
>   Term [] getTerms();

FWIW:   In KinoSearch, I have extract_terms set up to return either a  
Term, or in the case of PhraseQuery, a reference to an array of  
Terms.  When the Highlighter sees the arrayref, it knows to winnow  
down the positions that the term appears at, using the same logic as  
PhraseScorer.  This is what allows KinoSearch's Highlighter to handle  
phrases properly.

    http://www.rectangular.com/cgi-bin/uscon_search.cgi?q=%22united 
+states%22
    http://lucenebook.com/search?query=%22united+states%22

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/


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