lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <>
Subject [jira] Commented: (LUCENE-671) Hashtable based Document
Date Thu, 14 Sep 2006 19:28:23 GMT
    [ ] 
Doug Cutting commented on LUCENE-671:

The final declaration is not for performance.  It is to keep folks from thinking, if they
subclass Document, that instances of their subclass will be returned to them in search results.
 To make Documents fully-subclassible one would need to make their serialization extensible.

> Hashtable based Document
> ------------------------
>                 Key: LUCENE-671
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index, Search
>    Affects Versions: 2.0.0, 1.9
>            Reporter: Chris
>            Priority: Minor
>         Attachments:,
> I've attached a Document based on a hashtable and a performance test case. It performs
better in most cases (all but enumeration by my measurement), but likely uses a larger memory
footprint. The Document testcase will fail since it accesses the "fields" variable directly
and gets confused when it's not the list it expected it to be. 
> If nothing else we would be interested in at least being able to extend Document, which
is currently declared final. (Anyone know the performance gains on declaring a class final?)
Currently we have to maintain a copy of lucene which has methods and classes definalized and
> There are other classes as well that could be declared non-final (Fieldable comes to
mind) since it's possible to make changes for project specific situations in those aswell
but that's off-topic.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


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

View raw message