[
https://issues.apache.org/jira/browse/LUCENE-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498494#comment-14498494
]
ASF subversion and git services commented on LUCENE-6345:
---------------------------------------------------------
Commit 1674134 from [~mikemccand] in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1674134 ]
LUCENE-6345: add null checking for query parameters
> 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
> Fix For: Trunk, 5.2
>
> Attachments: LUCENE-6345.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
