[
https://issues.apache.org/jira/browse/LUCENE-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4096.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.0
> impossible to CheckIndex if you use norms other than byte[]
> -----------------------------------------------------------
>
> Key: LUCENE-4096
> URL: https://issues.apache.org/jira/browse/LUCENE-4096
> Project: Lucene - Java
> Issue Type: Task
> Components: core/index
> Affects Versions: 4.0
> Reporter: Robert Muir
> Fix For: 4.0, 5.0
>
> Attachments: LUCENE-4096.patch
>
>
> I noticed TestCustomNorms had the checkIndexOnClose disabled, but
> I think this is a real problem.
> If someone wants to use e.g. float[] norms, they should be able to run
> CheckIndex.
> CheckIndex is fine with validating any norm type, the problem is that it
> sometimes creates an IndexSearcher and fires off TermQueries for some
> calculations. This causes it to (wrongly) fail, because DefaultSimilarity
> expects single byte norms.
> I don't think CheckIndex needs to use TermQuery here, we can do this
> differently so it doesnt use IndexSearcher or TermQuery but just the postings
> apis.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
