Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 5 Mar 2009 14:42:26 -0800 (PST)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-dev@lucene.apache.org
Subject: Re: Getting tokens from search results.  Simple concept
In-Reply-To: <22247863.post@talk.nabble.com>
Message-ID: <Pine.LNX.4.64.0903051438560.31024@radix.cryptio.net>
References: <22225364.post@talk.nabble.com>
 <EB97EDD8-FFD4-4451-9E96-7E3A722C5178@ehatchersolutions.com>
 <22247863.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: What I would LOVE is if I could do it in a standard Lucene search like I
: mentioned earlier. 
: Hit.doc[0].getHitTokenList() :confused:
: Something like this...

The Query/Scorer APIs don't provide any mechanism for information like 
that to be conveyed back up the call chain -- mainly because it's more 
heavy weight then most people need.

If you have custom Query/Scorer implementations, you can keep track of 
whatever state you want when executing a QUery -- in fact the SpanQuery 
family of queries do keep track of exactly the type of info you seem to 
want, and after executing a query, you can ask it for the "Spans" of any 
matching document -- the down side is the a loss in performance of query 
execution (because it takes time/memory to keep track of all the matches)


-Hoss


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