[
https://issues.apache.org/jira/browse/LUCENE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889642#action_12889642
]
Uwe Schindler commented on LUCENE-2548:
---------------------------------------
bq. And I also agree about stopping interning field suddenly. What is the
reason for stop doing that?
I don't understand the question.
The reason for removing interning is to remove the cost of doing this without
need in trunk. The interning was solely done for speeding up typical TermEnum
iteration where each term's field need to be compared to detect a change. As
fields are now no longer coupled to terms and Term*s*Enums (TermEnum was
removed) only iterate over one field, this is useless and the cost for creating
terms does no retify to keep it.
> Remove all interning of field names from flex API
> -------------------------------------------------
>
> Key: LUCENE-2548
> URL: https://issues.apache.org/jira/browse/LUCENE-2548
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Uwe Schindler
> Fix For: 4.0
>
>
> In previous versions of Lucene, interning of fields was important to minimize
> string comparison cost when iterating TermEnums, to detect changes in field
> name. As we separated field names from terms in flex, no query compares field
> names anymore, so the whole performance problematic interning can be removed.
> I will start with doing this, but we need to carefully review some places
> e.g. in preflex codec.
> Maybe before this issue we should remove the Term class completely. :-)
> Robert?
--
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]