This is where things get exciting, when theory runs right up
against the particular problem at hand...
What if your document consisted of a content field (perhaps broken
into as many pieces as necessary) and multiple references?
Something like:
Document doc = new Document()
doc.add("content", ...
On Dec 15, 2008, at 12:44 PM, Chris Bamford wrote:
One question (thinking ahead now): how to differentiate between
content and reference hits if they are retrieved from the same
index? Presumably I will need to try to retrieve a field which only
exists in one and if it fails, I know it must
Hi Erick,
You raise some excellent points. First let me explain why our structure
is the way it is ..
There is not actually a strict 1-1 relationship between entries in the
two indexes. One represents content, the other, references.
There can only ever be 1 content item, but there can be seve
Stop it right now . You've gotta take off your DB hat and put
on your searching hat to get the most out of Lucene. So I'd
think about the following:
1> Why do you have two indexes? Why not just put all
the data into a single index? The fields are disjoint anyway
Note that there is no
Hi
I have a situation where I have two related indexes which are logically
linked by a common field called INDEXID. All other fields differ between
the two indexes. For any given INDEXID I would like to be able to
retrieve the matching pair of documents, one from each index. (Logically
this i
