You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2010/09/29 15:35:34 UTC
[jira] Reopened: (JCR-2669) Improve reading of cached UUID for
given document number
[ https://issues.apache.org/jira/browse/JCR-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger reopened JCR-2669:
-----------------------------------
Assignee: Marcel Reutegger
The most important part of this issue is not fixed yet. The changed to the CachingIndexReader were not included in the patch.
> Improve reading of cached UUID for given document number
> --------------------------------------------------------
>
> Key: JCR-2669
> URL: https://issues.apache.org/jira/browse/JCR-2669
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: JCR-2669.patch
>
>
> CachingIndexReader.document(int n, FieldSelector fieldSelector) creates a new
> Field from the cached UUID. The lucene Field implementation always does a
> String.intern() on the field name, which is quite slow. We should probably have
> our own implementation for that specific use case where we know that the name
> is already interned. e.g. UUIDField implements Fieldable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.