Hello Esteban, I am not sure about your particular issue, but the Lucene indexing structure changed yes (and will keep changing in the future). But apparently you have been programming against how this lucene index is structured. You hooked this in yourself I suppose?
Jackrabbit, just like specified in jsr 170, gives you a subset of xpath and sql as possible ways to query the repository data. Since this is an abstraction, people do not have to know how to write lucene queries *or* hoe the lucene index is structured. If from 1.3 -> 1.4 the lucene index is restructured, well, that is obviously possible. We can not guarantuee obviously that programming against assumptions made about how the index is structured keeps working. Hopefully you agree on this with me. OTOH, i might be off, and you mean something else? However, if you programm agains the lucene structure, make sure it is part of the structure which you control yourself. Otherwise you'll end up refactoring after every change -Ard > Hi all. > I have the following code that used to work in 1.3 Document > doc = hits.doc(i); String name = doc.get(FieldNames.LABEL); > Now with Jackrabbit 1.4 I get a null label. Digging, I saw > that when it reads the fields from the index, there's no label. > Was there any change between 1.3 and 1.4 regarding the fields > in a Lucene QueryHits result? > Or do I need to add the label somwhere, so I can later get it? > Regards, > > Esteban Franqueiro > [EMAIL PROTECTED] > > > Notice: This email message, together with any attachments, > may contain information of BEA Systems, Inc., its > subsidiaries and affiliated entities, that may be > confidential, proprietary, copyrighted and/or legally > privileged, and is intended solely for the use of the > individual or entity named in this message. If you are not > the intended recipient, and have received this message in > error, please immediately return this by email and then delete it. >
