|
If you were logged in you would be able to see more operations.
|
|
|
| Lucene Fields: |
Patch Available
|
| Resolution Date: |
11/Mar/08 08:07 AM
|
MultiFieldQueryParser.getFieldQuery(String, String, int) calls super.getFieldQuery(String, String), thus obliterating any slop parameter present in the query.
It should probably be changed to call super.getFieldQuery(String, String, int), except doing only that will result in a recursive loop which is a side-effect of what may be a deeper problem in MultiFieldQueryParser – getFieldQuery(String, String, int) is documented as delegating to getFieldQuery(String, String), yet what it actually does is the exact opposite. This also causes problems for subclasses which need to override getFieldQuery(String, String) to provide different behaviour.
|
|
Description
|
MultiFieldQueryParser.getFieldQuery(String, String, int) calls super.getFieldQuery(String, String), thus obliterating any slop parameter present in the query.
It should probably be changed to call super.getFieldQuery(String, String, int), except doing only that will result in a recursive loop which is a side-effect of what may be a deeper problem in MultiFieldQueryParser – getFieldQuery(String, String, int) is documented as delegating to getFieldQuery(String, String), yet what it actually does is the exact opposite. This also causes problems for subclasses which need to override getFieldQuery(String, String) to provide different behaviour. |
Show » |
made changes - 09/Mar/08 10:41 PM
| Field |
Original Value |
New Value |
|
Component/s
|
|
QueryParser
[ 12310234
]
|
made changes - 10/Mar/08 06:42 AM
|
Assignee
|
|
Doron Cohen
[ doronc
]
|
made changes - 11/Mar/08 08:07 AM
|
Lucene Fields
|
[New]
|
[Patch Available]
|
|
Resolution
|
|
Fixed
[ 1
]
|
|
Status
|
Open
[ 1
]
|
Resolved
[ 5
]
|
|
Bug
Resolved
Major
MultiFieldQueryParser ignores slop parameter
