Re: lucene gosen diff btn jars

2012-03-02 Thread Koji Sekiguchi
Hi Thushara, Please use lucene-gosen mailing list for lucene-gosen questions: http://groups.google.com/group/lucene-gosen Thanks, koji -- Query Log Visualizer for Apache Solr http://soleami.com/ (12/03/03 6:41), Thushara Wijeratna wrote: > I'm testing lucene-gosen for Japanese tokenization an

Re: CloseableThreadLocal problem

2012-03-02 Thread Matthew Bellew
Thanks for your reply MIke, I create this bug. https://issues.apache.org/jira/browse/LUCENE-3841 Matt On Thu, Mar 1, 2012 at 2:32 PM, Michael McCandless wrote: > Phew, tricky. > > The problem is purging is potentially costly... it iterates all > entries in the map (threads that have called get)

lucene gosen diff btn jars

2012-03-02 Thread Thushara Wijeratna
I'm testing lucene-gosen for Japanese tokenization and wondering what the differences are between the two jars provided. (ipadic / chaisen)? In my preliminary testing, I'm not seeing any difference in tokenization in these two jars. (the jar with no dictionary did not work, I assume I need to make

RE: Building FST-like automaton queries

2012-03-02 Thread Paul Hill
> > Wow, that was quick!  Thanks! > > The power of open source and coffee break, combined... 12 minutes! Wow, that is fast turnaround or a lot of coffee. -Paul

Re: In Lucene 3.5 is it always better to not optimize indexes ?

2012-03-02 Thread Paul Taylor
On 02/03/2012 18:58, Uwe Schindler wrote: Why not simply forceMerge your index one time and compare with unoptimized? Well its not straightforward for me to do that as the problem is only rearing its head on Production, and I don't have access to the Production machine. Paul - Uwe Schind

RE: In Lucene 3.5 is it always better to not optimize indexes ?

2012-03-02 Thread Uwe Schindler
Why not simply forceMerge your index one time and compare with unoptimized? - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Paul Taylor [mailto:paul_t...@fastmail.fm] > Sent: Friday, March 02, 2012 6:08 P

In Lucene 3.5 is it always better to not optimize indexes ?

2012-03-02 Thread Paul Taylor
I've updated codebase from 3.4 to 3.5 and as part of that took the advice to no longer optimize my indexes. During testing everything seemed okay but since releasing to Live noticed the load on the servers is about 50% higher. I made quite a few code changes in this release but its not obvious

Re: Lucene's use of vectors

2012-03-02 Thread Robert Muir
On Thu, Mar 1, 2012 at 6:15 PM, Mike O'Leary wrote: > In the Javadoc page for the Similarity class, it says, > > "Lucene combines Boolean model (BM) of Information Retrieval with Vector > Space Model (VSM) of Information Retrieval - documents "approved" by BM are > scored by VSM." > > Is the Vec

Re: Performance of MultiFieldQueryParser versus QueryParser

2012-03-02 Thread Ian Lea
Highly unlikely unless your subclass was slow for some reason. -- Ian. On Fri, Mar 2, 2012 at 7:31 AM, Paul Taylor wrote: > If I happen to subclass MultiFieldQueryParser unneccessarily (thought need > more than one default search but don't after all) would it  have any impact > on performance

Re: Range queries in successive positions

2012-03-02 Thread Ian Lea
Or take a look at search.regex.RegexQuery contrib module. You won't be able to use that via QueryParser either. It might make more sense to do the sanitizing before indexing rather than after. -- Ian. On Fri, Mar 2, 2012 at 7:26 AM, Trejkaz wrote: > On Fri, Mar 2, 2012 at 6:22 PM, su ha wro