[
https://issues.apache.org/jira/browse/LUCENENET-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625441#comment-13625441
]
Chris Eldredge commented on LUCENENET-519:
------------------------------------------
Thanks for the background. I searched for this issue but didn't find anything
relevant, so I wasn't sure if it was the same in Java and if it is a known
issue.
Your suggested work-around didn't quite work for me. When retrieving Documents
later at query time, the field value is blank for some reason and I wasn't able
to figure out why. It could be that I'm doing something wrong.
Anyway, another work-around I came up with that does work is using reflection
to set the {{internalOmitNorms}} field on {{AbstractField}} to false.
It would be nice if {{NumericField}} was not sealed so I didn't have to resort
to reflection, but I'm guessing this is a carry-over from Java too.
Thanks again for explaining the issue clearly.
> NumericField.Boost ignored at index time
> ----------------------------------------
>
> Key: LUCENENET-519
> URL: https://issues.apache.org/jira/browse/LUCENENET-519
> Project: Lucene.Net
> Issue Type: Bug
> Components: Lucene.Net Core
> Affects Versions: Lucene.Net 3.0.3
> Reporter: Chris Eldredge
> Priority: Minor
> Attachments: NumericFieldBoostTests.cs
>
>
> When adding a document that contains a NumericField with a boost value
> greater than 1.0f (the default), the boost value seems to be ignored.
> Querying later using a BooleanQuery does not boost the numeric field over
> other fields that have a default boost amount.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
