[
https://issues.apache.org/jira/browse/LUCENE-5260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790075#comment-13790075
]
Areek Zillur commented on LUCENE-5260:
--------------------------------------
Hey Michael, I was thinking about how to nicely replace TermFreqIterator.
- I was thinking about having some kind of wrapper for TermFreqPayloadIterator
that will nullify the payload field for the current TermFreqIterator consumers
and a way for the wrapper to signal early on to the consumers that they dont
need to deal with the payload at all.
- Also It seems like there are a lot of implementations for TermFreqIterator
(e.g BufferedTermFreqIteratorWrapper, SortedTermFreqIteratorWrapper); I will
make sure all these implementation work with TermFreqPayloadIterator and its
new wrapper (for mimicking TermFreqIterator).
Any thoughts? I will try to come up with a rough patch soon.
> Make older Suggesters more accepting of TermFreqPayloadIterator
> ---------------------------------------------------------------
>
> Key: LUCENE-5260
> URL: https://issues.apache.org/jira/browse/LUCENE-5260
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Areek Zillur
>
> As discussed in https://issues.apache.org/jira/browse/LUCENE-5251, it would
> be nice to make the older suggesters accepting of TermFreqPayloadIterator and
> throw an exception if payload is found (if it cannot be used).
> This will also allow us to nuke most of the other interfaces for
> BytesRefIterator.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
