[
https://issues.apache.org/jira/browse/LUCENE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2110:
----------------------------------
Attachment: LUCENE-2110-nextSeekTermUpd.patch
Here a small update that changed nextSeekTerm to also provide the current
TermRef. It will be null on first call. This removes the ugly if (unitialized)
code in Automaton.
I will now work on a better approach with only accept using an extended
AcceptStatus with next seek term). The current patch will now be committed.
> Refactoring of FilteredTermsEnum and MultiTermQuery
> ---------------------------------------------------
>
> Key: LUCENE-2110
> URL: https://issues.apache.org/jira/browse/LUCENE-2110
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Affects Versions: Flex Branch
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Fix For: Flex Branch
>
> Attachments: LUCENE-2110-nextSeekTermUpd.patch, LUCENE-2110.patch,
> LUCENE-2110.patch, LUCENE-2110.patch, LUCENE-2110.patch, LUCENE-2110.patch,
> LUCENE-2110.patch
>
>
> FilteredTermsEnum is confusing as it is initially positioned to the first
> term. It should instead work like an uninitialized TermsEnum for a field
> before the first call to next() or seek().
> FilteredTermsEnums cannot implement seek() as eg. NRQ or Automaton are not
> able to support this. Seeking is also not needed for MTQ at all, so seek can
> just throw UOE.
> This issue changes some of the internal behaviour of MTQ and
> FilteredTermsEnum to allow also seeking in NRQ and Automaton (see comments
> below).
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
