If you don't have a lot of entries for each invoice you can duplicate the
invoice for each entry - you'll have some field duplications (and bigger
index size) between the different invoices but it'll be easy to find exactly
what you want.
If you have too many different values, I built a solution s
There has been discussion in the past about how PhraseQuery artificially
requires that the Terms you add to it must be in the same field ... you
could theoretically modify PhraseQuery to have a tpe of query that
required terms in one field be withing (slop)N positions of a term in a
"parallel"
I'll provide a better example, perhaps it will help in formulating a
solution.
Suppose I am designing an index that stores invoices. One document
corresponds to one invoice, which has a unique id. Any number of employees
can make comments on the invoices, and comments have different
classification
Thanks for the suggestion, but I think I will need a more robust solution,
because this will only work with pairs of fields. I should have specified
that the example I gave was somewhat contrived, but in practice there could
be more than two parallel fields. I'm trying to find a general solution th
How about using variable field names?
url: http://www.cnn.com/
page_description: cnn breaking news
page_title_ajax: news
page_title_paris: cnn news
page_title_daniel: homepage
username: ajax
username: paris
username: daniel
and search for +user:ajax +page_title_ajax:news or maybe just
pag
Hello,
I am designing an index in which one url corresponds to one document. Each
document also contains multiple parallel repeating fields. For example:
Document 1:
url: http://www.cnn.com/
page_description: cnn breaking news
page_title: news
page_title: cnn news
page_titel: homepage
On Thursday 22 June 2006 21:18, Subodh Damle wrote:
> Hi all.
>
> We've been using Lucene to index our dynamic data structure and so far
> Lucene has been flexible enough to accommodate our requirements.
>
> Now we have this requirement about searching repeating fields,
: Here, the 'revenue-info' is a repeating node, so we can have records like :
: Record 1
: ---financial-data
: --revenue-info
: year = 2000
: amount = 100
: --revenue-info
: year = 2001
: amount = 200
:
: Record 2
: ---financial-data
: --revenue-
Hi all.
We've been using Lucene to index our dynamic data structure and so far
Lucene has been flexible enough to accommodate our requirements.
Now we have this requirement about searching repeating fields, whose
implementation is not clear.
Our data records have a dynamic tree
