RE: Unexpected Results - using should and must in boolean query

2010-09-17 Thread Uwe Schindler
Hah, I forgot that, thanks! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Chris Hostetter [mailto:hossman_luc...@fucit.org] > Sent: Friday, September 17, 2010 7:21 PM > To: java-user@lucene.apache.org

RE: Unexpected Results - using should and must in boolean query

2010-09-17 Thread Chris Hostetter
: If you have some MUST terms, but you also want to have at least one of a : list of other terms (like 5 SHOULD clauses), the trick is to separate both: : Create a BooleanQuery with 2 MUST clauses, one is your required TermQuery : and the second clause is itself a BooleanQuery with all the SHOULD

How to close the wrapped directory implementation

2010-09-17 Thread Pulkit Singhal
With RAMDirectory we have the option of providing another Directory implementation such as FSDirectory that can be wrapped and loaded into memory: Directory directory = new RAMDirectory(FSDirectory.open(new File(fileDirectoryName))); But after building the index, if I close the IndexWriter then t

Re: Connection question

2010-09-17 Thread Lance Norskog
This can probably be done. The hardest part is cross-correlating your Lucene analyzer use with the Solr analyzer stack definition. There are a few things Lucene does that Solr doesn't- span queries for one. Lance On Fri, Sep 17, 2010 at 12:39 PM, Christopher Gross wrote: > Yes, I'm asking about

Re: recommended way to identify a version to pass to StandardAnalyzer constructor?

2010-09-17 Thread Bill Janssen
Bill Janssen wrote: > ...is there any attribute or static > method somewhere in Lucene which will return a value of > org.apache.lucene.util.Version that corresponds to the version of the > code? That's what I'm looking for. Version.LUCENE_CURRENT looks good, > but it's deprecated. And, given

Re: recommended way to identify a version to pass to StandardAnalyzer constructor?

2010-09-17 Thread Bill Janssen
Simon Willnauer wrote: > On Fri, Sep 17, 2010 at 8:14 PM, Bill Janssen wrote: > > Simon Willnauer wrote: > > > >> Hey Bill, > >> let me clarify what Version is used for since I think that caused > >> little confusion. > > > > Thanks. > > > >> The Version constant was mainly introduced to help >

Re: Connection question

2010-09-17 Thread Christopher Gross
Yes, I'm asking about network connections. Are you aware of any documentation on how I can set up Solr to use the Lucene index that I already have? Thanks! -- Chris On Fri, Sep 17, 2010 at 3:02 PM, Ian Lea wrote: > Are you asking about network connections?  There is no networking > built int

Re: QueryParser in 3.x

2010-09-17 Thread Simon Willnauer
On Fri, Sep 17, 2010 at 7:34 PM, Scott Smith wrote: > First, let me say that I didn't think the problem was in QueryParser and I > apologize if that's how it sounded.  QueryParser is a central method to > Lucene.  1 of me having problems with QueryParser, 1000's of others not.  Is > the problem

Re: recommended way to identify a version to pass to StandardAnalyzer constructor?

2010-09-17 Thread Simon Willnauer
On Fri, Sep 17, 2010 at 8:14 PM, Bill Janssen wrote: > Simon Willnauer wrote: > >> Hey Bill, >> let me clarify what Version is used for since I think that caused >> little confusion. > > Thanks. > >> The Version constant was mainly introduced to help >> users with backwards compatibility and upgr

Re: Connection question

2010-09-17 Thread Ian Lea
Are you asking about network connections? There is no networking built into lucene. There is in solr, and lucene can use directories on networked file systems. -- Ian. On Fri, Sep 17, 2010 at 6:08 PM, Christopher Gross wrote: > I'm trying to connect to a Lucene index on a test server.  All o

Re: recommended way to identify a version to pass to StandardAnalyzer constructor?

2010-09-17 Thread Bill Janssen
Simon Willnauer wrote: > Hey Bill, > let me clarify what Version is used for since I think that caused > little confusion. Thanks. > The Version constant was mainly introduced to help > users with backwards compatibility and upgrading their codebase to a > new version of lucene without breaking

RE: QueryParser in 3.x

2010-09-17 Thread Scott Smith
First, let me say that I didn't think the problem was in QueryParser and I apologize if that's how it sounded. QueryParser is a central method to Lucene. 1 of me having problems with QueryParser, 1000's of others not. Is the problem more likely in my code or lucene. We'll all agree on the an

Connection question

2010-09-17 Thread Christopher Gross
I'm trying to connect to a Lucene index on a test server. All of the examples that I've found use a local directory to connect into the Lucene index, but I can't find one that will remotely hook into it. Can someone please point me in the right direction? I'm fairly certain that someone has run

Re: Filtering times stored as longs in HEX

2010-09-17 Thread Ian Lea
>From a quick look your code looks fine, but there are various possible reasons why you might not be getting the results you expect. http://wiki.apache.org/lucene-java/LuceneFAQ#Why_am_I_getting_no_hits_.2BAC8_incorrect_hits.3F Are the email and phone numbers stored as is, or analyzed? Does it wo

Re: recommended way to identify a version to pass to StandardAnalyzer constructor?

2010-09-17 Thread Simon Willnauer
Hey Bill, let me clarify what Version is used for since I think that caused little confusion. The Version constant was mainly introduced to help users with backwards compatibility and upgrading their codebase to a new version of lucene without breaking existing applications / indexes build with pre

Re: QueryParser in 3.x

2010-09-17 Thread Simon Willnauer
On Fri, Sep 17, 2010 at 1:06 AM, Scott Smith wrote: > I recently upgraded to Lucene 3.0 and am seeing some new behavior that I > don't understand.  Perhaps someone can explain why. > > > > I have a custom analyzer.  Part of the analyzer uses the AsciiFoldingFilter.   > If I run a word with an uml