[
https://issues.apache.org/jira/browse/LUCENE-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll resolved LUCENE-671.
------------------------------------
Resolution: Won't Fix
> Hashtable based Document
> ------------------------
>
> Key: LUCENE-671
> URL: https://issues.apache.org/jira/browse/LUCENE-671
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index, Search
> Affects Versions: 1.9, 2.0.0
> Reporter: Chris
> Priority: Minor
> Attachments: HashDocument.java, TestBenchDocuments.java
>
>
> 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 overriden.
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
