[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185533#comment-13185533
]
Uwe Schindler edited comment on LUCENE-3687 at 1/13/12 10:38 AM:
-----------------------------------------------------------------
bq. Why? this is really confusing! I think setByte should take byte, setInt
int, setLong, long etc.
I agree. That's also a problem in other DocValues use cases like sorting. The
SortField name uses INT but sorts by long and so on. There is already an issue
open: LUCENE-3192
was (Author: thetaphi):
Why? this is really confusing! I think setByte should take byte, setInt
int, setLong, long etc.
I agree. That's also a problem in other DocValues use cases like sorting. The
SortField name uses INT but sorts by long and so on. There is already an issue
open: LUCENE-3192
> 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]
