Number to printable sortable string, including floating point numbers and negatives

2008-09-10 Thread Jimi Hullegård
Hi, I'm was sure this discussion has come up before, but after looking around alot I haven't found a suitable answer. I have a need to index number fields that can be used for sorting and range queries, however the various solutions that I have seen does all have some kind of downside. First o

follow up of Lucene out of memory with RAMDirectory on J2EE environment

2008-09-10 Thread Chris Lu
This usually happens on J2EE environment, if you use RAMDirectory. Before Lucene-1195.(svn r659602, May23,2008), if you close() RAMDirectory, the resources will be released right away. After Lucene-1195.(svn r659602, May23,2008),If you simply close() the RAMDirectory, there will be an undetermined

Re: Replacing FAST functionality at sesam.no-ShingleFilter+exactmatching

2008-09-10 Thread Mck
> And if you have configured an analyzer that includes a query-time > filter, it should be invoked, regardless of whether a phrase query is > constructed. sorry steve i failed to explain this so clearly. Without phrasing the ShingleFilter is indeed invoked. But it is used three separate times for

RE: Re: Replacing FAST functionality at sesam.no-ShingleFilter+exactmatching

2008-09-10 Thread Steven A Rowe
On 09/10/2008 at 12:02 PM, Mck wrote: > > > But this does not return the hits i want. > > > > Have you tried submitting the query without quotes? (That's where the > > PhraseQuery likely comes from.) > > Yes. It does not work. It returns just the unigrams, again the same > behaviour as mentioned

Re: Search with multiple wildcards

2008-09-10 Thread Erick Erickson
Of course you can construct your own BooleanQuery programmatically. It's relatively easy, just try it. On Wed, Sep 10, 2008 at 11:52 AM, Sertic Mirko, Bedag <[EMAIL PROTECTED] > wrote: > Jep, this is what i have read. > > do I need to use the query parser, or can I create a query by the api? > I

Re: Replacing FAST functionality at sesam.no -ShingleFilter+exactmatching

2008-09-10 Thread Mck
> > But this does not return the hits i want. > > Have you tried submitting the query without quotes? (That's where the > PhraseQuery likely comes from.) Yes. It does not work. It returns just the unigrams, again the same behaviour as mentioned earlier. Debugging ShingleFilter in this case it

AW: Search with multiple wildcards

2008-09-10 Thread Sertic Mirko, Bedag
Jep, this is what i have read. do I need to use the query parser, or can I create a query by the api? Is there an example available? Thanks a lot Mirko -Ursprüngliche Nachricht- Von: Erick Erickson [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 10. September 2008 16:45 An: java-user@luce

RE: Understanding/controlling role of Weight in IndexSearcher

2008-09-10 Thread Steven A Rowe
Hi Micah, On 09/09/2008 at 11:57 PM, Micah Jaffe wrote: > I'm [...] curious how weights are calculated. [...] > thoughts? pointers? best practices? http://lucene.apache.org/java/docs/scoring.html - To unsubscribe, e-mail: [EMA

RE: RE: Re: Replacing FAST functionality at sesam.no -ShingleFilter+exactmatching

2008-09-10 Thread Steven A Rowe
Hi mck, On 09/10/2008 at 3:55 AM, Mck wrote: > > probably better to change the one instance of .setPositionIncrement(0) > > to .setPositionIncrement(1) - that way, MultiPhraseQuery will not be > > invoked, and the standard disjunction thing should happen. > > Tried this. > As you say i end up wit

Re: Search with multiple wildcards

2008-09-10 Thread Erick Erickson
Is this what you're referring to? Lucene supports single and multiple character wildcard searches within single terms (not within phrase queries). (from http://lucene.apache.org/java/docs/queryparsersyntax.html) I'm pretty sure you can have multiple *terms* with wildcards. Luke is your friend her

AW: Search with multiple wildcards

2008-09-10 Thread Sertic Mirko, Bedag
Hi Thank you for your quick response:-) Of course I need to use the * character :-) But I have read somewhere in the documentation that leading wildcards are not supported, and only one wildcard term per query. Is this limitation resolved in the current version? Regards Mirko -Ursprünglic

Re: Search with multiple wildcards

2008-09-10 Thread Erick Erickson
Sure, but you'll have to set the leading wildcard option, which I've forgotten the exact call, but it's in the docs. And use * rather than % . But wildcards are tricky, especially the TooManyClauses exception. You might want to peruse the archive for wildcard posts... Best Erick On Wed, Sep 10,

Search with multiple wildcards

2008-09-10 Thread Sertic Mirko, Bedag
[EMAIL PROTECTED] Is it possible to do a search with multiple wildcards in one query, for instance "%MANAGE%" AND "CORE%"? Is there a code example available? Thanks a lot Mirko

Re: Newbie question: using Lucene to index hierarchical information.

2008-09-10 Thread Marcelo Ochoa
Hi Leonid If you are not familiar with Oracle XMLDB schema mappings here an example of how to store WikiPedia XML dumps into Oracle database, but using XML-to-relational model: http://marceloochoa.blogspot.com/2007/12/uploading-wikipedia-dumps-to-oracle.html The structure of WikiPedia dumps s

RE: Re: Replacing FAST functionality at sesam.no - ShingleFilter+exactmatching

2008-09-10 Thread Mck
> [snip] The option thus should be named something like > "coterminalPositionIncrement". This seems like a reasonable addition, > and a patch likely would be accepted, if it included unit tests. Done. https://issues.apache.org/jira/browse/LUCENE-1380 ~mck -- "The only thing I know, is that I

Re: 10Gb of .nfsXXX files about a week old in NFS based index directory

2008-09-10 Thread Michael McCandless
David Loeng wrote: Hi, We have a customer using lucene on an NFS directory, which contains ~10Gb of .nfs files. These files are the means by which NFS implements delete-on-close semantics (that is, if the index writer commits a delete of a file that is still held open by an index r

Re: Newbie question: using Lucene to index hierarchical information.

2008-09-10 Thread Leonid M.
Hi Karsten, Thanks a lot. I finally have got Your idea. Ok, I think it's worth to do the real job now :) Thanks for the advices, finally I have understood the directions I could go for it. > > do you really need the "Complex scenario"? > what kind of query is your use case? My Query UC is smth

RE: Re: Replacing FAST functionality at sesam.no - ShingleFilter+exactmatching

2008-09-10 Thread Mck
> probably better to change the one instance of .setPositionIncrement(0) > to .setPositionIncrement(1) - that way, MultiPhraseQuery will not be > invoked, and the standard disjunction thing should happen. Tried this. As you say i end up with instead a PhraseQuery terms = { list_entry_shin