Re: Parameterized queries in Lucene

ed (passing it to the searcher) all > > parameters must be bound. > > So in terms of optimizations I was thinking that nothing would change. > > > > To make sure that we are all in the same page, I created a simple gist > [1] > > of how I had in mind to support

Re: Parameterized queries in Lucene

created a simple gist [1] > of how I had in mind to support parameterized queries in Lucene. > If you think that it is a bad idea then I will go back to the option of > recreating the query every time. > > Best, > Stamatis > > [1] https://gist.github.com/zabetak/ac2a8320c72779

Re: Parameterized queries in Lucene

sure that we are all in the same page, I created a simple gist [1] of how I had in mind to support parameterized queries in Lucene. If you think that it is a bad idea then I will go back to the option of recreating the query every time. Best, Stamatis [1] https://gist.github.com/zabetak

Re: Parameterized queries in Lucene

I agree with Atri that it makes little sense to support parameterized queries like this. Lucene not only uses field statistics but also term statistics, so we couldn't make decisions about the right way to execute this query before knowing what the value of `a.name` is. Supporting something like th

Re: Parameterized queries in Lucene

Hi Atri, Let's assume that we have the following simple SQL query over a Lucene index holding book authors. SELECT * FROM authors a WHERE a.name = ? AND a.age > 15 The where clause corresponds to a BooleanQuery combining a TermQuery and a IntPoint query. During the prepare phase of the SQL state

Re: Parameterized queries in Lucene

I am curious — what use case are you targeting to solve here? In relational world, this is useful primarily due to the fact that prepared statements eliminate the need for re planning the query, thus saving the cost of iterating over a potentially large combinatorial space. However, for Lucene, th

Parameterized queries in Lucene

Hi all, In the world of relational databases and SQL, the existence of parameterized queries (aka. PreparedStatement) offers many advantages in terms of security and performance. I guess everybody is familiar with the idea that you prepare a statement and then you execute it multiple times by jus

Unsupported queries in Lucene XML CoreParser

We are using Lucene 4.10.4 We parse query in one server and search happens in other servers(RMI call). Since the lucene query object is not serializable, we try to use XML Query Parser

Computing document frequencies for specific queries in Lucene

50 fields of /person/actor/movie_acted_in and 4 million documents... Thank you very much! -- View this message in context: http://lucene.472066.n3.nabble.com/Computing-document-frequencies-for-specific-queries-in-Lucene-tp3101450p3101450.html Sent from the Lucene - Java Users mailing list a

Re: FastSSFuzzy for faster fuzzy queries in Lucene

- Fast Similarity Search in Large Dictionaries. http://fastss.csg.uzh.ch/ - Paper: Fast Similarity Search in Large Dictionaries. http://fastss.csg.uzh.ch/ifi-2007.02.pdf - FastSimilarSearch.java http://fastss.csg.uzh.ch/FastSimilarSearch.java - Paper: Fast Similarity Search in Peer-to-Peer Networks

Re: FastSSFuzzy for faster fuzzy queries in Lucene

hi, yes, the results that come back from the lucene index i verify at runtime before expanding the query. i considered trying to store delete positions as payloads or something but fastssWC is good enough for me. i'll see about posting my code today. On Tue, Jan 6, 2009 at 4:52 AM, Thomas Bocek

Re: FastSSFuzzy for faster fuzzy queries in Lucene

hi, although i've been trying to get my code into shape to upload to jira (holidays got in the way a bit), I guess i think there might be some issues making my implementation work for general use. i based my design on certain assumptions, such as the fact I don't update indexes. once my index is

Re: FastSSFuzzy for faster fuzzy queries in Lucene

Do you have a reference paper/link on it? Sounds interesting. On Jan 5, 2009, at 8:17 PM, Jason Rutherglen wrote: Hello, I'm interested in getting FastSSFuzzy into Lucene, perhaps as a contrib module. One question is how much would the index grow? We've got a list of people's names we

FastSSFuzzy for faster fuzzy queries in Lucene

Hello, I'm interested in getting FastSSFuzzy into Lucene, perhaps as a contrib module. One question is how much would the index grow? We've got a list of people's names we want to do spellchecking on for example. -J

Re: Range queries in Lucene - numerical or lexicographical

U, because I didn't write the code? You can always contribute a patch. On 8/13/07, Mohammad Norouzi <[EMAIL PROTECTED]> wrote: > > Thanks Erick but unfortunately NumberTools works only with long primitive > type I am wondering why you didn't put some method for double and float. > > > > On 8/1

Re: Range queries in Lucene - numerical or lexicographical

: Subject: Re: Range queries in Lucene - numerical or lexicographical : : Thanks. Probably this should be mentioned on the documentation page. it does say right above the "date" example: " Sorting is done lexicographically." (Admitedly I'm not sure why the word

Re: Range queries in Lucene - numerical or lexicographical

Thanks Erick but unfortunately NumberTools works only with long primitive type I am wondering why you didn't put some method for double and float. On 8/13/07, Nilesh Bansal <[EMAIL PROTECTED]> wrote: > > Thanks. Probably this should be mentioned on the documentation page. > > -Nilesh > > On 8/12

Re: Range queries in Lucene - numerical or lexicographical

Thanks. Probably this should be mentioned on the documentation page. -Nilesh On 8/12/07, Erick Erickson <[EMAIL PROTECTED]> wrote: > As has been discussed several times, Lucene is a string-only engine, and > has no native understanding of numerical values. You have to normalize > them for string

Re: Range queries in Lucene - numerical or lexicographical

As has been discussed several times, Lucene is a string-only engine, and has no native understanding of numerical values. You have to normalize them for string searches. See NumberTools. Best Erick On 8/11/07, Nilesh Bansal <[EMAIL PROTECTED]> wrote: > > Hi all, > > Lucene query parser synax page

Range queries in Lucene - numerical or lexicographical

Hi all, Lucene query parser synax page (http://lucene.apache.org/java/docs/queryparsersyntax.html) provides the following two examples of range query: mod_date:[20020101 TO 20030101] and title:{Aida TO Carmen} Now my question is, numerically 10 is greater than 2, but in string-only comparison 2 i

RE: Queries in Lucene

fore, and we thought that we could reused the index and apply a special query for that Thanks for your help. Best regards Teresa -Mensaje original- De: Erick Erickson [mailto:[EMAIL PROTECTED] Enviado el: miércoles, 13 de septiembre de 2006 14:20 Para: java-user@lucene.apache.org As

Re: Queries in Lucene

I'm assuming that you're new to Lucene, so if you're an old pro you probably already know all this I think you'll have difficulty here. Lucene has no concept of lines, just tokens and offsets. So here are a couple of suggestions off the top of my head... If the first line is the *only* way

Queries in Lucene

Hi all, I´ve got a index and now I´m trying to create a query with lucene-2.0.0, I´d like to find files that in the first line get the following: AND Word2 I´m tried with the package org.apache.lucene.demo.SearchFiles but I get files where the word "Word2" is not in the first line. I don´t k

Re: How to combine multiple fielded queries in Lucene

ED]> To: java-user@lucene.apache.org Sent: Thu, 27 Oct 2005 10:24:34 -0500 Subject: How to combine multiple fielded queries in Lucene I am developing a search application via Lucene and ran into a problem can be described as: Assume we have document schema with these fields: Title,

Re: How to combine multiple fielded queries in Lucene

On 27 Oct 2005, at 11:32, Peter Kim wrote: If you're using the QueryParser, you just prefix the field-specific part with the field. For example, the query in your email should be submitted to the query parser as: (Title:"baseball" OR Summary:"white sox") AND Publication_date:"199501 TO 200

RE: How to combine multiple fielded queries in Lucene

x27;ll cost to buy the book. Peter > -Original Message- > From: Xin Herbert Wu [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 27, 2005 11:25 AM > To: java-user@lucene.apache.org > Subject: How to combine multiple fielded queries in Lucene > > I am develop

How to combine multiple fielded queries in Lucene

I am developing a search application via Lucene and ran into a problem can be described as: Assume we have document schema with these fields: Title, Author, Summary, Publication_date(Date), Content The user query is like this: Find all documents where either Title field has word "baseba