lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wmartinusa@gmail.com" <wmartin...@gmail.com>
Subject Re: Understanding Query Parser Behavior
Date Mon, 21 Nov 2016 17:46:25 GMT
No
Sent from my LG G4, an AT&T 4G LTE smartphone
------ Original message------From: Peru RedmiDate: Mon, Nov 21, 2016 10:44 AMTo: java-user@lucene.apache.org;Cc:
Subject:Understanding Query Parser Behavior
Hello All ,Could someone explain *QueryParser* behavior on these cases1. While Indexing ,Document
doc = new Document();doc.add(new Field("*Field*", "*http://www.google.com*", Field.Store.YES,
Field.Index.ANALYZED));      index has *two* terms - *http* & *www.google.com**2.* While
searching ,Analyzer anal = new *ClassicAnalyzer*(Version.LUCENE_30, newStringReader(""));QueryParser
parser=new *MultiFieldQueryParser*(Version.LUCENE_30, newString[]{"*Field*"},anal);Query query
= parser.parse("*http://www.google.com *");Now , query has *three *terms  -  (Field:http)
*(Field://)* (Field:www.google.com)i) Why I have got 3 terms while parsing , and 2 terms on
indexing (Usingsame ClassicAnalyzer in both cases ) ?ii) is this expected behavior of ClassicAnalyzer(Version.LUCENE_30)
onParser ?iii) what should be done to avoid query part *(Field://) *?Thanks,Peru.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message