You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2018/07/07 13:51:00 UTC

[jira] [Commented] (LUCENE-8386) Maybe a DocIdSetIterator may implement Bits?

    [ https://issues.apache.org/jira/browse/LUCENE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535762#comment-16535762 ] 

Adrien Grand commented on LUCENE-8386:
--------------------------------------

Do you have concrete ideas in mind? I see BitSetIterator as an exception, other Bits-based iterators don't perform well and are better implemented with two-phase iterators?

> Maybe a DocIdSetIterator may implement Bits?
> --------------------------------------------
>
>                 Key: LUCENE-8386
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8386
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>            Reporter: David Smiley
>            Priority: Minor
>
> I was looking at ConjunctionDISI and noted the special case logic for DISI's of type BitSetIterator. It seems to only need the more minimal Bits interface though it makes references to BitSet specifically.   BitSetIterator is a concrete class; it would be nice if a DISI could either implement an optional interface to expose a Bits or perhaps implements Bits directly.  This would allow other/custom DISIs that can implement a Bits quickly without being forced to use BitSetIterator specifically.  Even DocIdSetIterator.all(...) could implement this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org