CrommVardek opened a new issue, #785:
URL: https://github.com/apache/lucenenet/issues/785
Using Lucene.Net 4.8.0-beta00016, the indexer index object with a field in
Document specifically used for sorting like this :
`new TextField("lastname-sort", person.LastName.RemoveDiacritics(),
Field.Store.NO)`
However when searching with sort using new SortField("lastname-sort",
SortFieldType.STRING, false) will return some scoreDocs (the first ones) with
fields to null, which is odd to me.
After researching in the doc
(https://lucenenet.apache.org/docs/4.8.0-beta00008/api/Lucene.Net/Lucene.Net.Search.Sort.html?q=sort)
- that is not up-to-date, because using new Field is deprecated and using
Field.Index.NOT_ANALYZED is also deprecated.
Note that if the fields of the ScoreDocs hits are not null, they are
correctly sorted. It is always the same Documents that have fields to NULL. So
if they are part of the result, the sorted result is invalid.
Note, all fields (Field.Store.YES) are stored except for two used for
sorting.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@lucenenet.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
