Is there a syntax to set the term position in a query built with
queryparser? For example, I would like something like:
PhraseQuery q = new PhraseQuery();
q.add(t1, 0);
q.add(t2, 0);
q.setSlop(0);
As I understand it, the slop defaults to 0, but I don't know how to
search for basically two tokens
On Wed, Mar 4, 2009 at 4:41 PM, Grant Ingersoll wrote:
> You might have a look at Droids (http://incubator.apache.org/droids/) or
> Nutch (http://lucene.apache.org/nutch) and their communities. They are much
> more focused on crawling (not to say there aren't people here who crawl,
> just saying
On Thu, Mar 26, 2009 at 6:28 PM, Matt Schraeder wrote:
> I'm new to Lucene and just beginning my project of adding it to our web
> app. We are indexing data from a MS SQL 2000 database and building
> full-text search from it.
>
> Everything I have read says that building the index is a resource h
On Tue, Apr 7, 2009 at 3:08 AM, Jinming Zhang wrote:
> Hi,
>
> I have the following situation which needs to customize the final score
> according to field value.
>
> Suppose there are two docs in my query result, and they are ordered by
> default score sort:
>
> doc1(field1:bookA, field2:2000-01-
On Wed, Apr 8, 2009 at 11:45 AM, addman wrote:
>
> Hi,
> Is it possible to create a query to search a field for any value? I just
> need to know if the optional field contain any data at all.
google for: lucene field existence
There's no way built in, one strategy[1] is to have a 'meta field
2009/4/10 Matthew Hall :
> I think I would tackle this in a slightly different manner.
>
> When you are creating this index, make sure that that field has a
> default value. Make sure this value is something that could never appear
> in the index otherwise. Then, when you goto place this field into
On Sat, Apr 11, 2009 at 12:25 PM, Erick Erickson
wrote:
> That'll teach me to scan a post. The link I sent you
> is still relevant, but wildcards are NOT intended to be used to
> concatenate terms. You want a phrase query or a span query
> for that. i.e. "A C F"~# where # is the "slop", that is, t
On Sun, Apr 12, 2009 at 5:56 AM, Erik Hatcher
wrote:
>
> On Apr 11, 2009, at 9:11 PM, Tim Williams wrote:
>
>> On Sat, Apr 11, 2009 at 12:25 PM, Erick Erickson
>> wrote:
>>>
>>> That'll teach me to scan a post. The link I sent you
>>> is stil
ot;name", "F")) },
2,
true);
If you wanted to still use the QueryParser, Erik was suggesting you
could extend it and override "getFieldQuery" (there's a good example
of this in LIA I think) to, essentially, generate the query above.
--tim
> Erik Hatc
On Fri, Apr 17, 2009 at 7:27 PM, Newman, Billy wrote:
> I am looking for info on how to use the IndexWriter.update method. A short
> example of how to add a document and then later update would
> be very helpful. I get lost because I can add a document with just the
> document, but I need a do
On Thu, May 21, 2009 at 1:12 PM, Michael McCandless
wrote:
> Sorry for the slow response.
>
> It's really not clear when 2.9 will be released. We have accumulated
> a number of good improvements -- higher performance field sorting, new
> higher performance Collector (replaces HitCollector) API,
>
On Wed, Jun 17, 2009 at 3:16 PM, vanshi wrote:
>
> Hello all,
>
> I have a situation where a field is indexed like this
> (FAC_NAME(Field.Store.NO, Field.Index.NO_NORMS)) and keyword analyzer is
> used on this field. Although, I'm aware that NO_NORMS doesn't use any
> analyzer.
>
> Now, the query +
12 matches
Mail list logo
