Solr Or Lucene Paging

Hi，All： I want to ask a question, How does Solr implements Paging, such as start = 100 and row = 20 I roughly saw Solr source, hare is the code: getDocListNC(QueryResult qr,QueryCommand cmd) ; often it uses : topCollector = TopFieldCollector.create(weightSort(cmd.getSort()), len, false

RE: TopDocCollector vs TopScoreDocCollector (semantics changed in 4.0, not backward comptabile)

Hi, This is not a bug in Lucene 4.0. This behavior is unchanged since Lucene 2.9/3.0, you just don't read javadocs and you just don't seem to understand the changes since Lucene 2.9. I just repeat one final time: Collector is a low level search component in Lucene and was introduced in Lucene

RE: TopDocCollector vs TopScoreDocCollector (semantics changed in 4.0, not backward comptabile)

Thanks a lot. Really appreciate your help here. I have read through the document and understand that the IndexReader uses sub readers (to look into the index files) and AtomicReader does not. But how does this affect from the search stand point of view. I think search results should be consistent

Re: Migrating SnowballAnalyzer to 4.1

Hi Peng, The short answer: EnglishAnalyzer will behave differently in terms of stemming than SnowballAnalyzer("English", StopAnalyzer.ENGLISH_STOP_WORDS). PorterStemmer, which is used by the EnglishAnalyzer in analyzers-common, is an older version of the English Snowball stemmer (now called Eng

Multiple field values with the same position in the index

Hello! I'm thinking on a way of implementing the search with word ambiguity in Lucene. Say, a word "duck" appears in a document at the position 10. It has 2 Part-of-Speech tags: "Noun" and "Verb". And I want to recover this position both for POS:Noun and POS:Verb queries. So can you please point

RE: Migrating SnowballAnalyzer to 4.1

Hi Steve, Thanks for the help. One more question: Is EnglishAnalyzer a drop-in replacement for SnowballAnalyzer("English", ...), in terms of stemming? Thanks again Peng PS Sorry for the Thread Hijacking. Will behave the next time. > -Original Message- > From: Steve Rowe [mailto:sar...@

Re: Migrating SnowballAnalyzer to 4.1

: Subject: Migrating SnowballAnalyzer to 4.1 : References: : : : In-Reply-To: : https://people.apache.org/~hossman/#threadhijack Thread Hijacking on Mailing Lists When starting a new discussion on a mailing list, please do not reply to an existing message, instead start a fresh emai

Re: Migrating SnowballAnalyzer to 4.1

Hi Peng, Take a look at the release docs: In particular, in the API Javadocs section, the analyzers-common documentation has a large list of per-language analyzers. EnglishAnalyzer is under the org.apache.lucene.analysis.en package:

RE: TopDocCollector vs TopScoreDocCollector (semantics changed in 4.0, not backward comptabile)

Hi, I answered you question parallel to your second mail. This is not a new change in Lucene 4, its like that since Lucene 2.9/3.0. You may also read: http://blog.thetaphi.de/2012/02/is-your-indexreader-atomic-major.html The comment to your code: Don't pass a IndexReader to the ctor of your co

Migrating SnowballAnalyzer to 4.1

Hi, I have a Lucene 2.9.x app that uses org.apache.lucene.analysis.snowball.SnowballAnalyzer for index generation, analyzer = new SnowballAnalyzer("English", StopAnalyzer.ENGLISH_STOP_WORDS); and I want to upgrade it to 4.1. SnowballAnalyzer is deprecated in 4.1. The doc simply states "Depr

RE: TopDocCollector vs TopScoreDocCollector (semantics changed in 4.0, not backward comptabile)

Could someone please comment on the above code snippet ? Also, one observation is that our search results are not consistent if we are using* IndexReader vs AtomicReader?* Could this be a problem? Thanks, Sai. -- View this message in context: http://lucene.472066.n3.nabble.com/TopDocCollector

Re: lucene 4 index

2013/2/28 ash nix : > Hi, > > Can anyone please send me document on lucene 4 index format? > Want to know internals of index. It is part of the Lucene documentation. http://lucene.apache.org/core/4_1_0/core/org/apache/lucene/codecs/lucene41/package-summary.html#package_description --dho > -- >

Re: More questions on BlockJoinQuery

Sorry, I meant to say "in the directory navigation dialog that comes up, choose the *directory* containing Lucene and Solr (*not* a proejct file)". - Steve On Feb 28, 2013, at 9:22 AM, Steve Rowe wrote: > Chris, > > You shouldn't use File > New Project, which will run you through creating > m

Re: More questions on BlockJoinQuery

Chris, You shouldn't use File > New Project, which will run you through creating modules, etc. Rather, you should use File > Open (in versions of IntelliJ prior to v12 this was File > Open Project), navigate in the directory navigation dialog that comes up to the *directory* containing Lucene

Re: More questions on BlockJoinQuery

Hi guys, Still struggling with this I'm afraid :-( I have now downloaded lucene_solr_4_1_0 and have run 'ant idea' and 'ant generate-maven-artifacts'. However, when I load the codebase into IntelliJ with File > New Project ... I can see the code but am unable to right-click / Run any of the unit