mikemccand commented on PR #12426: URL: https://github.com/apache/lucene/pull/12426#issuecomment-1630910575
It will indeed be very costly in some cases, and likely should only be used in a test context. Maybe we move this to `test-framework`, and rename to `SlowVerifyingQuery`? Or ... does Lucene have any index-time enforcement / optional support for fields that are double (inverted & forward) indexed for use at search time with `IndexOrDocValuesQuery`, to ensure (maybe even enforce) that precisely the same value was indexed both ways? We have the recently added `KeywordField` for string type fields (I think?) for this case, but do we have something for numerics too? If not, it seems trappy today that one can have an inconsistent index and then think they can safely use `IndexOrDocValuesQuery`... we should also update `IndexOrDocValuesQuery` javadocs to point to `KeywordField` for indexing and its factories for generating efficient queries. -- 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-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
