lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (LUCENE-778) Allow overriding a Document
Date Mon, 05 Mar 2007 10:02:50 GMT


Nicolas Lalevée commented on LUCENE-778:

Note that I was talking about the future API, with some deprecated functions removed. So the
API will look like :
class IndexReader {
  ReturnableDocument doc(int n);
class IndexWriter {
  void addDocument(IndexableDocument doc);

1) it does matter from the user point of view : we cannot do anymore writer.addDocument(reader.doc(10)).

2) Effectively I can implement a DecoratedDocument. But I cannot make Lucene instanciating
my own document, the reader will still return some ReturnableDocument. Unless you want to
allow the user to customize in Lucene the instanciation of Document by providing a factory
of Document ?

> Allow overriding a Document
> ---------------------------
>                 Key: LUCENE-778
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: Nicolas Lalevée
>            Priority: Trivial
> In our application, we have some kind of generic API that is handling how we are using
Lucene. The different other applications are using this API with different semantics, and
are using the Lucene fields quite differently. We wrote some usefull functions to do this
mapping. Today, as the Document class cannot be overriden, we are obliged to make a document
wrapper by application, ie some MyAppDocument and MyOtherAppDocument which have a property
holding a real Lucene Document. Then, when MyApp or MyOtherApp want to use our generic lucene
API, we have to "get out" the Lucene document, ie do some genericLuceneAPI.writeDoc(myAppDoc.getLuceneDocument()).
This work fine, but it becomes quite tricky to use the other function of our generic API which
is genericLuceneAPI.writeDocs(Collection<Document> docs).
> I don't know the rational behind making final Document, but removing it will allow more
object-oriented code.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message