[
https://issues.apache.org/jira/browse/LUCENE-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947067#comment-13947067
]
Mikhail Khludnev commented on LUCENE-5052:
------------------------------------------
[~mikemccand] let's agree on desired functionality:
* this posting format should wrap the standard one, like pulsing;
* if IndexOptions.DOCS_ONLY is provided, this codec suppresses standard posting
format and write the bitset file (<<should-be>> explore fancy formats then);
* same logic applies on reading;
I wonder what’s the correct behavior if docEnum is requested with FLAG_FREQS,
should it silently returns 1 on freq() or throwing exception?
Let me ask one off-top question about switching to PulsingPF. I've heard that
it's enabled _automatically_ for id-like field. Can you point on where it's
done particularly? Does it works for Lucene only, or for Solr also?
Thanks
> bitset codec for off heap filters
> ---------------------------------
>
> Key: LUCENE-5052
> URL: https://issues.apache.org/jira/browse/LUCENE-5052
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/codecs
> Reporter: Mikhail Khludnev
> Labels: features
> Fix For: 5.0
>
> Attachments: LUCENE-5052.patch, bitsetcodec.zip, bitsetcodec.zip
>
>
> Colleagues,
> When we filter we don’t care any of scoring factors i.e. norms, positions,
> tf, but it should be fast. The obvious way to handle this is to decode
> postings list and cache it in heap (CachingWrappingFilter, Solr’s DocSet).
> Both of consuming a heap and decoding as well are expensive.
> Let’s write a posting list as a bitset, if df is greater than segment's
> maxdocs/8 (what about skiplists? and overall performance?).
> Beside of the codec implementation, the trickiest part to me is to design API
> for this. How we can let the app know that a term query don’t need to be
> cached in heap, but can be held as an mmaped bitset?
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
