lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (LUCENE-2317) allow separate control of whether docTermFreq and positions are indexed
Date Sat, 13 Mar 2010 15:22:35 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael McCandless resolved LUCENE-2317.
----------------------------------------

    Resolution: Duplicate

Duh, this is a dup of LUCENE-2048.  I can't keep track of all the particles anymore!

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message