[
https://issues.apache.org/jira/browse/LUCENE-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2846:
--------------------------------
Attachment: LUCENE-2846.patch
here's an updated patch:
* The IR.setNorm(float) is also removed, forcing the user to use the correct
similarity versus us using the wrong one (the static)
* MultiNorms doesn't fake norms anymore, instead it handles the case of
non-existent field versus omitted norms.
* When a document doesnt have a field, its (undefined) norms are written as
zero bytes instead of Similarity.getDefault().encodeNorm(1f).
* All uses of Similarity.get/setDefault are now gone in lucene core, except for
in IndexSearcher and IndexWriterConfig.
> 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
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
