[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3687:
------------------------------------
Attachment: LUCENE-3687.patch
new patch
* renamed setXXX to setDouble, setFloat etc.
* moved Norm our of similarity and merged it with DocValueNorm
* use UOE in simpletext and 3x norms
* utilize normValueType to actually not write norms if only bogus norms would
be written. Lucene4 can now check if norms are present without looking at the
directory.
this patch actually doesn't even write norms if not absolutely needed. Do we
have any requirement that this needs to happen even if there is not a single
doc with norms in that field? I removed all the crazy 0 value writing in
NormsConsumer and still all tests pass. If there is a case where these bogus
norms are required we need to have a test for it.
> Allow similarity to encode norms other than a single byte
> ---------------------------------------------------------
>
> Key: LUCENE-3687
> URL: https://issues.apache.org/jira/browse/LUCENE-3687
> Project: Lucene - Java
> Issue Type: New Feature
> Components: core/index, core/search
> Affects Versions: 4.0
> Reporter: Simon Willnauer
> Fix For: 4.0
>
> Attachments: LUCENE-3687.patch, LUCENE-3687.patch, LUCENE-3687.patch,
> LUCENE-3687.patch
>
>
> LUCENE-3628 cut over norms to docvalues. This removes the long standing
> limitation that norms are a single byte. Yet, we still need to expose this
> functionality to Similarity to write / encode norms in a different format.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
