Re: Analyzer Does Not Works As Accepted

>>I fixed the problems. StopFilter was not working as accepted because of letter cases. Alternatively, you could have moved StopFilter above the WordDelimiterFilter in your analysis chain. Regards Pravesh -- View this message in context: http://lucene.472066.n3.nabble.com/Analyzer-Do

Re: Lucene Retrieve Previous and Next Tokens At Analyzed Index

Hi, A little bit of details would further help. Any examples? Also what is the use-case for this? Regards -- View this message in context: http://lucene.472066.n3.nabble.com/Lucene-Retrieve-Previous-and-Next-Tokens-At-Analyzed-Index-tp4120076p4120340.html Sent from the Lucene - Java Users ma

Re: Lucene Token Attributes internal data structure

Just figured out myself by debugging the Lucene source code. Regards Pravesh -- View this message in context: http://lucene.472066.n3.nabble.com/Lucene-Token-Attributes-internal-data-structure-tp4110668p4110875.html Sent from the Lucene - Java Users mailing list archive at Nabble.com

Lucene Token Attributes internal data structure

javadocs that all AttributeSources maintain a single instance of an Attribute, then, how does a stream of tokens(CharTermAttribute better),positions,offsets is stored internally. Any pointers? Regards Pravesh -- View this message in context: http://lucene.472066.n3.nabble.com/Lucene-Token

Re: Lucene sort performance roots?

You might be doing search+sort together in a single query. Since lucene beats RDBMs in text search, so, could be that you are actually benefitting from the text search+sort, which would otherwise be slow on RDBMS. Thanx Pravesh -- View this message in context: http://lucene.472066.n3.nabble.com