You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2022/04/04 17:35:21 UTC

[GitHub] [lucene] jtibshirani commented on pull request #749: LUCENE-10466: IndexSortSortedNumericDocValuesRangeQuery unconditionally assumes the usage of the LONG-encoded SortField

jtibshirani commented on PR #749:
URL: https://github.com/apache/lucene/pull/749#issuecomment-1087829315

   @nknize I'm sorry about that, I missed that you wanted to discuss this before merging. I see this fix as a self-contained improvement -- previously we silently accepted but then failed on integer, float, or double sort fields, whereas now we handle and document them. The query is in sandbox and it doesn't seem like a big problem it doesn't support float/ double fields for now. Could you explain the open question you'd like to resolve?


-- 
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: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org