pylucene 3.5.0-3

[pylucene.git] / lucene-java-3.4.0 / lucene / contrib / xml-query-parser / src / test / org / apache / lucene / xmlparser / TermsQuery.xml

diff --git a/lucene-java-3.4.0/lucene/contrib/xml-query-parser/src/test/org/apache/lucene/xmlparser/TermsQuery.xml b/lucene-java-3.4.0/lucene/contrib/xml-query-parser/src/test/org/apache/lucene/xmlparser/TermsQuery.xml
deleted file mode 100644 (file)
index f1bf348..0000000
--- a/lucene-java-3.4.0/lucene/contrib/xml-query-parser/src/test/org/apache/lucene/xmlparser/TermsQuery.xml
+++ /dev/null
@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-               <!-- 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>
\ No newline at end of file