LUCENE-6367: correct CHANGES entry: PrefixQuery already operated in binary term space

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1669577 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Michael McCandless 2015-03-27 13:17:14 +00:00
parent b51277fecf
commit f60b1d12fc
1 changed files with 3 additions and 5 deletions

View File

@ -217,6 +217,9 @@ API Changes
-> .totalMaxDoc and MergePolicy.OneMerge.totalDocCount ->
.totalMaxDoc (Adrien Grand, Robert Muir, Mike McCandless)
* LUCENE-6367: PrefixQuery now subclasses AutomatonQuery, removing the
specialized PrefixTermsEnum. (Robert Muir, Mike McCandless)
Other
* LUCENE-6248: Remove unused odd constants from StandardSyntaxParser.jj
@ -244,11 +247,6 @@ Changes in Runtime Behavior
* LUCENE-6298: SimpleQueryParser returns an empty query rather than
null, if e.g. the terms were all stopwords. (Lee Hinman via Robert Muir)
* LUCENE-6367: PrefixQuery now subclasses AutomatonQuery, removing the
specialized PrefixTermsEnum. PrefixQuery now operates in binary
term space, meaning any binary term (not just valid UTF-8 terms)
are accepted. (Robert Muir, Mike McCandless)
======================= Lucene 5.0.0 =======================
New Features