[jira] Resolved: (LUCENE-2846) omitTF is viral, but omitNorms is anti-viral.

["Robert Muir (JIRA)" <ji...@apache.org>]

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

Robert Muir resolved LUCENE-2846.
---------------------------------

    Resolution: Fixed

Committed revision 1058367.

I deprecated the dangerous setNorm(float) method in 3.x in revision 1058370,
instead pointing at setNorm(byte) and using Similarity.encodeNormValue(),
so you can ensure your Similarity is always used (not Similarity.getDefault)


> omitTF is viral, but omitNorms is anti-viral.
> ---------------------------------------------
>
>                 Key: LUCENE-2846
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2846
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: 4.0
>
>         Attachments: LUCENE-2846.patch, LUCENE-2846.patch, LUCENE-2846.patch, LUCENE-2846.patch
>
>
> omitTF is viral. if you add document 1 with field "foo" as omitTF, then document 2 has field "foo" without omitTF, they are both treated as omitTF.
> but omitNorms is the opposite. if you have a million documents with field "foo" with omitNorms, then you add just one document without omitting norms, 
> now you suddenly have a million 'real norms'.
> I think it would be good for omitNorms to be viral too, just for consistency, and also to prevent huge byte[]'s.
> but another option is to make omitTF anti-viral, which is more "schemaless" i guess.

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