Hi Koji,
Thank you for your reply. I did try the QueryScorer without success, but
I was using Lucene 2.4.x
I noticed in the upgrade documentation that some changes had been made
relative to QueryScorer and QueryTermScorer in 3.1. I thought I would
check if someone else had come up with a solution
Stephen Greene wrote:
Hi Koji,
Thank you for your reply. I did try the QueryScorer without success, but
I was using Lucene 2.4.x
Hi Steve,
I thought you were using 2.9 or later because you mentioned
FastVectorHighlighter in your previous mail (FVH was first
introduced in 2.9). If I remembe
I am struggling to use PayTermQuery because of PayloadFunction. I didnt find
any example of PayTermQuery.
I am already using BoostTermQuery but I am not able to extract payload
value.
I am using example mention in
http://www.lucidimagination.com/blog/2009/08/05/getting-started-with-payloads/commen
I am building an online application where I want to provide search
functionality to users and each user is to search only within his own data.
Can you give me some ideas about the structure of the index that I should
have in this scenario? I know I could use a different index per user account
but t
No really better ways that spring to mind. At root you have to somehow
know what document is added by each user, and adding a field to
the document with this info is quite reasonable, then just tack
on an +user: to each query.
You can get creative with Lucene Filters. That is, create a Filter for
