You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Chris (JIRA)" <ji...@apache.org> on 2006/09/14 17:23:23 UTC
[jira] Updated: (LUCENE-671) Hashtable based Document
[ http://issues.apache.org/jira/browse/LUCENE-671?page=all ]
Chris updated LUCENE-671:
-------------------------
Attachment: HashDocument.java
> Hashtable based Document
> ------------------------
>
> Key: LUCENE-671
> URL: http://issues.apache.org/jira/browse/LUCENE-671
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index, Search
> Affects Versions: 2.0.0, 1.9
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org