[
https://issues.apache.org/jira/browse/LUCENE-9416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156599#comment-17156599
]
Mohammad Sadiq commented on LUCENE-9416:
----------------------------------------
I fixed {{CheckIndex}} to print the norm count using {{Long.toUnsignedString}}
but I'm not sure how to test it without having to build my own {{Similarity}}
class to be able to inject {{Long.MAX_VALUE}} as a norm. Any thoughts on how I
can test this?
PS: I didn't change the Jira state to "patch available" because I don't have a
test-case for this fix yet.
> Fix CheckIndex to print norms as unsigned integers
> --------------------------------------------------
>
> Key: LUCENE-9416
> URL: https://issues.apache.org/jira/browse/LUCENE-9416
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Reporter: Mohammad Sadiq
> Priority: Minor
> Attachments: LUCENE-9416.patch
>
>
> In the [discussion on "CheckIndex complaining about -1 for norms value" in
> the java-user list|http://markmail.org/message/gcwdhasblsyovwc2], it was
> identified that we should "fix CheckIndex to print norms as unsigned
> integers".
> I'd like to take a stab at this.
> I'm trying to understand the problem and from what I gather, while norms are
> `byte`s, the API exposes them as `long` values. While printing the error
> message, we want it to print a zero instead of -1?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
