Re: a faster way to addDocument and get the ID just added?

2011-03-30 Thread Simon Willnauer
On Wed, Mar 30, 2011 at 8:14 AM, Li Li wrote: > merge will also change docid > all segments' docId begin with 0 for all released version this is not true. Before trunk (and I think its in 3.1 also) merge only merged continuous segments so the actual per-segment ID might change but the global docu

Re: Filter to retrieve random documents without specific terms ?

2011-03-30 Thread Ian Lea
If your query explicitly excludes certain terms then surely you can be confident that matched docs will not contain those terms, and if your random docs are a subset of those matched docs they won't contain them either. -- Ian. On Tue, Mar 29, 2011 at 11:01 PM, Patrick Diviacco wrote: > One la

Spatial search: collect distances

2011-03-30 Thread Dmytro Barabash
Hi all! I need 1) sort search results by distance from some point and 2) show these distances for end-user together with other document information. 1) is simple – like an example in “Lucene in action”: there are latitude and longitude fields for each document in index, MyDistanceComparatorSource (

Re: Spatial search: collect distances

2011-03-30 Thread Dmytro Barabash
I am sorry to trouble, problem solved (in fact problem is absent :) ). Calculated distances saved in ScoreDoc (actually FieldDoc). 2011/3/30 Dmytro Barabash : > Hi all! > I need 1) sort search results by distance from some point and 2) show > these distances for end-user together with other docum

Re: a faster way to addDocument and get the ID just added?

2011-03-30 Thread Devon H. O'Dell
2011/3/30 Simon Willnauer : > On Wed, Mar 30, 2011 at 8:14 AM, Li Li wrote: >> merge will also change docid >> all segments' docId begin with 0 > > for all released version this is not true. Before trunk (and I think > its in 3.1 also) merge only merged continuous segments so the actual > per-segm

minimum string length for proximity search

2011-03-30 Thread Andy Yang
Is there a minimum string length requirement for proximity search? For example, would "a~" or "an~" trigger proximity search? The result would be horrible if there is no such requirement. Thanks, Andy - To unsubscribe, e-mail: ja

Re: minimum string length for proximity search

2011-03-30 Thread Erick Erickson
Uhhhm, doesn't "term1 term2"~5 work? If not, why not? You might get some use from http://lucene.apache.org/java/2_4_0/queryparsersyntax.html Or if that's not germane, perhaps you can explain your use case. Best Erick On Wed, Mar 30, 2011 at 5:49 PM, Andy Yang wrote: > Is there a minimum string

Re: minimum string length for proximity search

2011-03-30 Thread Andy Yang
We are trying to do proximity search for multi-terms and we don't care the order of the terms. Therefore "term1 term2"~5 probably will not get you "term2 term1" if both terms are long. So instead of applying distance at the end, we apply distance to each word, "term1~2 term2~2". I am wondering if w

Re: minimum string length for fuzzy search

2011-03-30 Thread Andy Yang
My question should really be on "fuzzy search". Is there a minimum length requirement for fuzzy search to start? For example, would "an~0.8" kick off fuzzy search? Thanks, Andy On Wed, Mar 30, 2011 at 4:02 PM, Erick Erickson wrote: > Uhhhm, doesn't "term1 term2"~5 work? If not, why not? > > You

Re: a faster way to addDocument and get the ID just added?

2011-03-30 Thread Trejkaz
On Wed, Mar 30, 2011 at 8:21 PM, Simon Willnauer wrote: > Before trunk (and I think > its in 3.1 also) merge only merged continuous segments so the actual > per-segment ID might change but the global document ID doesn't if you > only add documents. But this should not be considered a feature. In >