jpountz commented on pull request #477: URL: https://github.com/apache/lucene/pull/477#issuecomment-982379755
> I suspect almost nobody cares about this previous empty string crap It's about fields that produce no tokens so it's more than empty strings, it can also be fields that only contain punctuation and stop words (e.g. "to be or not to be" with EnglishAnalyzer). It's probably still a bit of an edge case but we changed the semantics of `exists` queries to only match fields that have tokens years ago and got a couple bug reports, e.g. https://github.com/elastic/elasticsearch/issues/7348. It's a pity that it doesn't allow us to better optimize this case but I can understand why these semantics can make sense if users want to find all documents for which they provided one or more values at index time. Maybe we could have both NormFieldsExistsQuery and TokensExistQuery and cross-link them via javadocs explaining differences and how `TokensExistQuery` might be faster. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
