| <?xml version="1.0" encoding="UTF-8"?> |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| <!-- TermsQuery uses an analyzer to tokenize text and creates a BooleanQuery with nested |
| "should" TermQueries for each of the tokens encountered. This can be used for user input |
| which may include content or characters that would otherwise be illegal query syntax when |
| using the standard lucene query parser. Of course the downside is that none of the query |
| operators (AND NOT ~ ^ : etc) will have an effect. For some scenarios queries are |
| not formed by people familiar with Lucene query syntax and they can inadvertently type illegal |
| query syntax so in these cases this is an appropriate and simple alternative |
| --> |
| <TermsQuery fieldName="contents">sumitomo bank</TermsQuery> |
