[ https://issues.apache.org/jira/browse/LUCENE-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lee Hinman updated LUCENE-6345: ------------------------------- Attachment: LUCENE-6345.patch Here's a patch that adds a lot of null checks to Querys as well as things like {{BooleanClause}}. It doesn't add tests for every single query for this (yet), though I see there are some already for {{FilteredQuery}}. Should I work on adding tests for every query type for this, or are adding the checks alone sufficient? > null check all term/fields in queries > ------------------------------------- > > Key: LUCENE-6345 > URL: https://issues.apache.org/jira/browse/LUCENE-6345 > Project: Lucene - Core > Issue Type: Bug > Reporter: Robert Muir > Attachments: LUCENE-6345.patch > > > See the mail thread "is this lucene 4.1.0 bug in PerFieldPostingsFormat". > If anyone seriously thinks adding a null check to ctor will cause measurable > slowdown to things like regexp or wildcards, they should have their head > examined. > All queries should just check this crap in ctor and throw exceptions if > parameters are invalid. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org