You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/03/19 05:17:15 UTC
[jira] [Created] (LUCENE-4854) DocTermsOrd getOrdTermsEnum() buggy,
lookupTerm/termsEnum is slow
Robert Muir created LUCENE-4854:
-----------------------------------
Summary: DocTermsOrd getOrdTermsEnum() buggy, lookupTerm/termsEnum is slow
Key: LUCENE-4854
URL: https://issues.apache.org/jira/browse/LUCENE-4854
Project: Lucene - Core
Issue Type: Bug
Reporter: Robert Muir
Fix For: 5.0, 4.3, 4.2.1
Investigating a test failure in grouping/ I found the current dv api needs help for DocTermsOrds (this facet+grouping collector uses seekExact(BytesRef) on the termsenum):
* termsenum.seekExact is slow because the default implementation calls lookupTerm, which is slow. but this thing already has an optimal termsenum it can just return directly (since LUCENE-4819)
* lookupTerm is slow because the default implementation binary-searches ordinal space, calling lookupOrd and comparing to the target. However, lookupOrd is slow for this thing (must binary-search ordinal space again, then next() at most index_interval times).
* its getOrdTermsEnum() method is buggy: doesn't position correctly on an initial next(). Nothing uses this today, but if we want to return this thing directly it needs to work: its just a trivial check contained within next()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org