[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973018#action_12973018
]
Robert Muir commented on LUCENE-2694:
-------------------------------------
bq. I would leave those as they are or only pull ord into TermState.
I agree about docfreq, but ord should go. Ord should be in e.g.
StandardTermState, but not in TermState nor TermsEnum.
This is an implementation detail for our current terms dictionary, and its
silly how we just throw UOE for other codecs:
Its codec-specific. Other terms implementations might have "something like an
ord" but it definitely might not even be a long!
Within StandardCodec etc this creates no problem as it still has access to it.
If we find ourselves wanting/needing to use ord
outside of Standard we should ask ourselves why this is and instead fix the
APIs to not depend on some codec-specific long value.
> MTQ rewrite + weight/scorer init should be single pass
> ------------------------------------------------------
>
> Key: LUCENE-2694
> URL: https://issues.apache.org/jira/browse/LUCENE-2694
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-2694-FTE.patch, LUCENE-2694.patch,
> LUCENE-2694.patch, LUCENE-2694.patch, LUCENE-2694.patch
>
>
> Spinoff of LUCENE-2690 (see the hacked patch on that issue)...
> Once we fix MTQ rewrite to be per-segment, we should take it further and make
> weight/scorer init also run in the same single pass as rewrite.
--
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]
