[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186335#comment-13186335
]
Robert Muir commented on LUCENE-3687:
-------------------------------------
{quote}
I kind of like the separation here. DocValues is really the Codec side of
things and it would be nice if we would not mix that stuff in the similarity
API.
{quote}
But what is the use case of having a separate Abstract class (Norm) from an
implementation class (DocValueNorm) that the codec doesn't even provide (its
instantiated as DocValues by normsconsumer[perfield] directly.
If we are going to have separate classes, then norm should be abstract and the
codec should provide the implementation. But we need a real use case as to why
a codec would need to customize the implementation of Norm to justify this.
> 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-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]
