rmuir commented on PR #12141: URL: https://github.com/apache/lucene/pull/12141#issuecomment-1425878966
Right, leaving the PointInSetQuery unoptimized but optimizing the slower one (TermInSetQuery) illustrates the issues with "database features". Anywhere else in the luce search engine, you'd use the faster, more appropriate datastructure (Points in this case) But with database features user has their `varchar` ID in some database somewhere they are using for joins, which will be slower, and no intention of fixing that :) Hopefully it helps to explain my frustration with such features. -- 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
