[
https://issues.apache.org/jira/browse/LUCENE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889610#action_12889610
]
Robert Muir commented on LUCENE-2548:
-------------------------------------
bq. I think it's a nice API, and for most cases, a term will still be a Term
and not a BytesRef + Field
Even if a term is a Term, a Term now is always a BytesRef + field behind the
scenes anyway.
bq. Isn't it a convenient class?
Basically, this is why i didnt go this route of removing it (instead modifying
Term class to work with bytesref).
The problem I saw was: if we have to modify tons of code to get rid of it, so
would users too on upgrading.
> 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]
