IndexReader.openIfChanged Doesn't Work on MultiReader

2011-12-02 Thread Jordon Saardchit
Just checking if this is a known issue or if I should report it. I have a MultiReader made up of 3 different indexes. If changes are made to either of the 3 underlying indexes, isCurrent() returns false (correctly) on said MultiReader. However, if I use the method IndexReader.openIfChanged() o

Re: Get Analyzed/Tokenized Field List

2010-12-24 Thread Jordon Saardchit
; fine because any INDEXED > field can use the your custom analyzer. > > But if you use different analyzers for different searchable fields, there's > no way I know of to > analyze an index and answer the question "what analyzer was this field > created with", > t

Re: Get Analyzed/Tokenized Field List

2010-12-23 Thread Jordon Saardchit
> documents > would be expensive... > > Why do you want to know? Perhaps there's another way to satisfy the > use-case. > > I could be way off base here, I'm speaking from general principles not > knowledge of > the code... > > Best >

Re: Get Analyzed/Tokenized Field List

2010-12-23 Thread Jordon Saardchit
? Jordon On Dec 23, 2010, at 1:30 PM, Erick Erickson wrote: > Have you looked at IndexReader.getFieldNames()? > > Best > Erick > > On Thu, Dec 23, 2010 at 3:23 PM, Jordon Saardchit wrote: > >> Is there an easy way to retrieve a collection of fields (or field names) >

Get Analyzed/Tokenized Field List

2010-12-23 Thread Jordon Saardchit
Is there an easy way to retrieve a collection of fields (or field names) that are analyzed/tokenized from any given index? Jordon - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail:

Re: Matching Documents BitSet

2010-10-05 Thread Jordon Saardchit
2.x? > > > -- > Ian. > > > On Mon, Oct 4, 2010 at 8:10 PM, Jordon Saardchit wrote: >> In lucene 3, is there an equivalent to obtaining a BitSet of documents from >> an Index as there was in version 2.x? I'm trying to put to

Matching Documents BitSet

2010-10-04 Thread Jordon Saardchit
In lucene 3, is there an equivalent to obtaining a BitSet of documents from an Index as there was in version 2.x? I'm trying to put together an upgrade path. Thanks! - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.

Re: Lucandra - Any experiences?

2010-09-03 Thread Jordon Saardchit
Hence my reluctance :) Jordon On Sep 3, 2010, at 5:44 AM, Michel Nadeau wrote: > Anyone? > > - Mike > aka...@gmail.com > > > On Mon, Aug 23, 2010 at 4:01 PM, Jordon Saardchit wrote: > >> I also would be thoroughly interested in hearing the viewpoints from any &

Re: Lucandra - Any experiences?

2010-08-23 Thread Jordon Saardchit
I also would be thoroughly interested in hearing the viewpoints from any lucandra users. Its a model we've been considering for some time now. Our only reluctance is the lack of point of views from the community. Good or bad, i'd love to hear experiences with it. Jordon On Aug 23, 2010, at

Lucene on NFS/iSCSI

2009-06-01 Thread Jordon Saardchit
So I've read a lot about nightmares with lucene over shared indices using NFS, and was curious if anyone had any experience running Lucene over iSCSI? Specifically if the same sort of lock failure issues occur as does with NFS. I'm specifically looking into multple machines mounted to a SAN v

RE: QueryParser Default Operator

2008-08-21 Thread Jordon Saardchit
Nvm, Extremely goofy project configuration here and classpath issues with much older versions. Ignore me! -Original Message- From: Jordon Saardchit [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2008 11:54 AM To: java-user@lucene.apache.org Subject: QueryParser Default Operator

QueryParser Default Operator

2008-08-21 Thread Jordon Saardchit
This may have been answered before, but is there a reason why setting the default operator on a QueryParser throws a java.lang.NoSuchFieldError??? QueryParser parser = new QueryParser( "title", new TokenAnalyzerImpl() ); parser.setDefaultOperator( QueryParser.AND_OPERATOR ); // This line throws t

QueryWrapperFilter performance

2008-06-27 Thread Jordon Saardchit
Hello All, Sort of new to lucene but have a general question in regards to performance. I've got a single index of rather large size (about 7 million docs). I've ran a couple different queries against it, which are described below. * WildcardQuery: (*term*) Which returns roughly 12000 hits i