[
https://issues.apache.org/jira/browse/LUCENE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844897#action_12844897
]
Shai Erera commented on LUCENE-2317:
------------------------------------
This will turn into another setting. Can we introduce on the fly a setMatchOnly
method which will turn all off (in addition to the one you're proposing)? Maybe
it should become its own FieldType constant ... it will be bundling together a
bunch of options that can be set individually if one wants finer grained
control.
> allow separate control of whether docTermFreq and positions are indexed
> -----------------------------------------------------------------------
>
> Key: LUCENE-2317
> URL: https://issues.apache.org/jira/browse/LUCENE-2317
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Michael McCandless
> Fix For: 3.1
>
>
> [Spinoff of LUCENE-2308... we keep spinning things off... I feel like we live
> inside a particle accelerator]
> Right now Lucene indexes the docTermFreq and positions into the postings, by
> default.
> You can use omitTFAP to turn them both off, which if you also omit norms
> gives you "match only" scoring.
> But, really, they ought to be separately controllable -- one may want to
> include docTermFreq but not positions, to get full scoring for non-positional
> phrases.
> Probably we should wait until LUCENE-2308 is done, and make the API change on
> *FieldType.
--
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
