Hello,
I am trying to add spatial search functionality to my application, but
having a trouble regarding lucene's spatial search.
It's very simple functionality: searching all items within given radius from
given starting point.
My current starting location is 37.504602,127.049031.
When I set
geo_distance = distances.get(hits.id(i));
double distance = DistanceUtils.getInstance().getDistanceMi(lat, lng, rsLat,
rsLng);
double llm = DistanceUtils.getInstance().getLLMDistance(lat, lng, rsLat,
rsLng);
System.out.println("Name: "+ name +", Distance (res, ortho, harvesine
Hello,
I am trying to add spatial search functionality to my application, but having a
trouble regarding lucene's spatial search.
It's very simple functionality: searching all items within given radius from
given starting point.
My current starting location is 37.504602,127.049031.
When I set se
meta city , it'll give you the results
for metacity , how do i solve this issue ? is there any concepts behind
indexing ?? please anyone let me know
--
View this message in context:
http://old.nabble.com/search-problem-tp26111084p26124737.html
Sent from the Lucene - Java Users mailing list ar
29 okt 2009 kl. 12.12 skrev m.harig:
i've a doubt in search , i've a word in my index welcomelucene
(without
spaces) , when i search for welcome lucene(with a space) , am not
able to
get the hits. It should pick the document welcomelucene.. is there
anyway to
do it ? i've used wildcar
ocument welcomelucene.. is there anyway
> to
> do it ? i've used wildcard option too. but no results , please anyone help
> me..
> --
> View this message in context:
> http://www.nabble.com/search-problem
but no results , please anyone help
me..
--
View this message in context:
http://www.nabble.com/search-problem-tp26111084p26111084.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Rajiv2 [mailto:rajiv.roo...@gmail.com]
> Sent: Friday, October 02, 2009 8:05 PM
> To: java-user@lucene.apache.org
> Subject: Lucene 2.9 Spatial
gt; org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:253)
>
> Does anyone have any clue as to what the problem might be?
>
> --
> View this message in context:
> http://www.nabble.com/Lucene-2.9-Spatial-Search-Problem-tp25719978p25719978.html
> Sent from the L
Searcher.search(IndexSearcher.java:253)
Does anyone have any clue as to what the problem might be?
--
View this message in context:
http://www.nabble.com/Lucene-2.9-Spatial-Search-Problem-tp25719978p25719978.html
Sent from the Lucene - Java Users mailing list archiv
oth will be found.
> >
> > I would suspect that I should not have to enter the wildcard in this
> case.
> >
> > In addition if a field contains a single alphanumeric term such as abc123
> > then search for abc does not find a match without the wildcard as well.
> &g
out the wildcard as well.
>
> Thanks
>
--
View this message in context:
http://www.nabble.com/Alphanumeric-Search-Problem-tp23514324p23515165.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To un
found.
I would suspect that I should not have to enter the wildcard in this case.
In addition if a field contains a single alphanumeric term such as abc123
then search for abc does not find a match without the wildcard as well.
Thanks
--
View this message in context:
http://www.nabble.com/Alph
a-user@lucene.apache.org
Sent: Wednesday, March 11, 2009 2:35:02 PM
Subject: Re: search problem when indexed using Field.setOmitTf()
This is expected: phrase searches will not work when you omitTf.
omitTf means positional information about tokens is not saved in
the index.
Span queries & p
27;s more self-descriptive.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Michael McCandless
To: java-user@lucene.apache.org
Sent: Wednesday, March 11, 2009 2:35:02 PM
Subject: Re: search problem when indexed using Field.setOmitTf()
This is
even consider renaming this so it's more self-descriptive.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael McCandless
> To: java-user@lucene.apache.org
> Sent: Wednesday, March 11, 2009 2:35:02 PM
> Subject: Re: searc
Siraj Haider wrote:
Yonik Seeley wrote:
On Wed, Mar 11, 2009 at 2:35 PM, Michael McCandless
wrote:
This is expected: phrase searches will not work when you omitTf.
But why would a phrase query be created? The code given looks like
it
should create a boolean query with two terms.
Of
Yonik Seeley wrote:
> On Wed, Mar 11, 2009 at 2:35 PM, Michael McCandless
> wrote:
>
>> This is expected: phrase searches will not work when you omitTf.
>>
>
> But why would a phrase query be created? The code given looks like it
> should create a boolean query with two terms.
>
> Of cour
On Wed, Mar 11, 2009 at 2:35 PM, Michael McCandless
wrote:
> This is expected: phrase searches will not work when you omitTf.
But why would a phrase query be created? The code given looks like it
should create a boolean query with two terms.
Of course, the given code also uses "" as the default
This is expected: phrase searches will not work when you omitTf.
omitTf means positional information about tokens is not saved in the
index. Span queries & phrase queries require that positional
information to work.
Mike
Siraj Haider wrote:
We are having a problem running searches on an
We are having a problem running searches on an index after upgrading to
2.4 and using the new Field.setOmitTf() function. The index size has
been dramatically reduces and even the search performace is better. But
searches do not return any results if searching for something that has a
space i
r@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you
could verify:
I have the following for my indexer:
public void add(Document document) {
IndexWriter indexWriter =
IndexWriterF
ument);
}
}
finally
{
commitAndOptimise()
}
HTH
Shashi
- Original Message
From: Amin Mohammed-Coleman
To: java-user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you
co
eader for
example
{
indexWriter.addDocument(document);
}
}
finally
{
commitAndOptimise()
}
HTH
Shashi
- Original Message
From: Amin Mohammed-Coleman
To: java-user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi ag
To: java-user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you
could verify:
I have the following for my indexer:
public void add(Document document) {
IndexWrit
iginal Message
From: Amin Mohammed-Coleman
To: java-user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you
could verify:
I have the following for my indexer:
public void add(Doc
user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you
could verify:
I have the following for my indexer:
public void add(Document document) {
IndexWriter indexWr
ashi
- Original Message
From: Amin Mohammed-Coleman
To: java-user@lucene.apache.org
Sent: Saturday, January 3, 2009 4:02:52 AM
Subject: Re: Search Problem
Hi again!
I think I may have found the problem but I was wondering if you could verify:
I have the following for my indexer:
pu
Hi again!
I think I may have found the problem but I was wondering if you could
verify:
I have the following for my indexer:
public void add(Document document) {
IndexWriter indexWriter =
IndexWriterFactory.createIndexWriter(getDirectory(), getAnalyzer());
try {
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
Well, your query results are consistent with what Luke is
reporting. So I'd go back and test your assumptions. I
suspect that you're not indexing what you think you are.
For your test document, I'd just print out what you're indexing
and the field it's going into. *for each field*. that is, every
Hi Erick
Thanks for your reply.
I have used luke to inspect the document and I am some what confused.
For example when I view the index using the overview tab of Luke I get
the following:
1 bodytest
1 id 1234
1 namertfDocumentToIndex.rtf
1 pathrtfD
Casing is usually handled by the analyzer. Since you construct
the term query programmatically, it doesn't go through
any analyzers, thus is not converted into lower case for
searching as was done automatically for you when you
indexed using StandardAnalyzer.
As for why you aren't getting hits, it
Hi
I have tried this and it doesn't work. I don't understand why using
"amin" instead of "Amin" would work, is it not case insensitive?
I tried "test" for field "body" and this works. Any other terms don't
work for example:
"document"
"indexed"
these are tokens that were extracted when
Basically Lucene stores analyzed tokens, and looks up for the matches based
on the tokens.
"Amin" after StandardAnalyzer is "amin", so you need to use new Term("body",
"amin"), instead of new Term("body", "Amin"), to search.
--
Chris Lu
-
Instant Scalable Full-Text Search
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
Hi
Sorry I was using the StandardAnalyzer in this instance.
Cheers
On 2 Jan 2009, at 00:55, Chris Lu wrote:
You need to let us know the analyzer you are using.
--
Chris Lu
-
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
You need to let us know the analyzer you are using.
--
Chris Lu
-
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.dbsight.com
Lucene Database Search in 3 minutes:
http://wiki.dbsight.com/index.php?title=Create_L
Hi
I have created a RTFHandler which takes a RTF file and creates a
lucene Document which is indexed. The RTFHandler looks like
something like this:
if (bodyText != null) {
Document document = new Document();
Field field = new Field(MetaDataEnum.BODY.getDescri
>Chain lChain = (Chain)pValue;
>>lField = new Field(pName,lChain.getName(),pStore, pIndex);
>>pDocument.add(lField);
>>}
>>}
>>
>> so here, where chain object is null I am saving the value to be
>> "
"nullnull".
The query I would use to retrieve what is null looks like
"chainName:nulllnull".
This solve everything I was looking for.
Thanks,
-Amar
-- Forwarded message --
From:
Date: Wed, Dec 24, 2008 at 11:33 AM
Subject: Re: Lucene search problem
To: java-use
24, 2008 at 11:33 AM
Subject: Re: Lucene search problem
To: java-user@lucene.apache.org
hi Erick,
I agree lucene do not index the object. in the following example I have
quoted fields are indexed as chain.chainName.
I am able to retrieve recipe objects using FullTextQuery as
"chain.chainName
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
AUTOMATIC REPLY
LUX is closed until 5th January 2009
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
Dec 23, 2008 at 12:04 AM, Aaron Schon
> > wrote:
> >
> > > I would second Erick's recommendation - create an arbitrary
> > representation
> > > for NULL such as "NULL" (if you are certain the term "NULL" does not
> > occur
> > > in actual
ur
> > in actual docs. Alternatively, use "NULLNULNULLNULL" or something to that
> > effect.
> >
> >
> >
> > - Original Message
> > From: Erick Erickson
> > To: java-user@lucene.apache.org
> > Sent: Monday, December 22, 2008 8:58:21
e
> From: Erick Erickson
> To: java-user@lucene.apache.org
> Sent: Monday, December 22, 2008 8:58:21 AM
> Subject: Re: Lucene search problem
>
> Try searching the mailing list archives for a fuller discussion, but
> the short answer is usually to index an unique value for you
From: Erick Erickson
To: java-user@lucene.apache.org
Sent: Monday, December 22, 2008 8:58:21 AM
Subject: Re: Lucene search problem
Try searching the mailing list archives for a fuller discussion, but
the short answer is usually to index an unique value for your
"null" entries, then
Try searching the mailing list archives for a fuller discussion, but
the short answer is usually to index an unique value for your
"null" entries, then search on that, something totally
outrageous like, say AAABBBCCCDDDEEEFFF.
Alternatively, you could create, at startup time, a
Filter of all the d
Hi,
I have problem with lucene search, I am quite new to this. Can some body
help or just push me to who can please.
Problem what I am facing we need search for object whose attribute "chain"
contaning null, but lucene does not help indexing the null values..
how can I achieve this, or please gu
D'oh!
Of course - I'm using StandardAnalyzer. Changing to a
PerFieldAnalyzerWrapper with a KeywordAnalyzer for
that field fixes the issue.
Thanks so much for fast response.
Ulf
--- Ian Lea <[EMAIL PROTECTED]> wrote:
> Hi
>
>
> I bet you are using an analyzer that is downcasing
> isbn:00714
Hi
I bet you are using an analyzer that is downcasing isbn:007149216X to
isbn:007149216x. I've been there! Options include creating the query
programmatically, using PerFieldAnalyzerWrapper, downcasing everything
yourself in advance. Or convert to ISBN-13.
--
Ian.
On Fri, May 16, 2008 at 10
Hello-
I'm experiencing a weird issue searching an index. The
index has information about books, and one of the
fields is the ISBN number. It is stored in the index
in untokenized form to enable searches by ISBN. So a
query like "isbn:0071490833" would return the Document
for that book. But it doe
P.S.
The Hibernate Search forum is at
http://forum.hibernate.org/viewforum.php?f=9
John G.
-Original Message-
From: oyesiji [mailto:[EMAIL PROTECTED]
Sent: Friday, May 02, 2008 5:24 PM
To: java-user@lucene.apache.org
Subject: Hibernate search (Problem adding new Record)
I am
);
} ^
|
.index causes a reindex not a save
John G.
-Original Message-
From: oyesiji [mailto:[EMAIL PROTECTED]
Sent: Friday, May 02, 2008 5:24 PM
To: java-user@lucene.apache.org
Subject: Hibernate search (Problem adding new Record)
I am using Hibernate Search in my Application, the first
riginal Message
> From: oyesiji <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Saturday, May 3, 2008 1:23:42 AM
> Subject: Hibernate search (Problem adding new Record)
>
>
> I am using Hibernate Search in my Application, the first time i attempt to
> ind
I am using Hibernate Search in my Application, the first time i attempt to
index records from the database it works and the second time i attempt to
add records i notice that it does not work
FullTextSession fullTextSession = Search.createFullTextSession(session);
for (JobDescription jobD
You can't tokenize the the search query if its on that field...using
maybe a per field analyzer and the keyword analyzer? Check em out if you
havn't.
On Fri, 2008-04-25 at 16:01 +0100, Chris Mannion wrote:
> Hi All
>
> I'm going to start this with an apology because, as you'll see below, I've
> p
Have you tried double-quoting the postcode instead of
using parentheses:
postcode:"M11 1LQ"
Ulf
--- Chris Mannion <[EMAIL PROTECTED]>
wrote:
> "(postcode:(M11 1LQ) )"
>
> However, the postcode search never returns any results.
__
Hi All
I'm going to start this with an apology because, as you'll see below, I've
probably missed out something quite fundamental about how Lucene works.
However, I'll explain the problem, we have a system setup which indexes and
searches records about business properties. One of the fields we i
a character or text appeared before the hyphen may cause the
>> pbroblem, if the text before hyphen is a number its work fine.
>> anybody can help me to correct this problem.
>>
>> Thanks
>> reeja
>>
>>
>> --
>> View this message i
: Search query is like this ttl:co-operative it returns more than 50 results,
: but if i convert the query like this ttl:co-operat* it returns no result.
: again i entered a query ttl:11-amino it returns some results, then changed
: the above query into ttl:11-amino* it will return some more res
turn some more results than
> previous query.
> I think if a character or text appeared before the hyphen may cause the
> pbroblem, if the text before hyphen is a number its work fine.
> anybody can help me to correct this problem.
>
> Thanks
> reeja
>
>
> --
> View
rrect this problem.
Thanks
reeja
--
View this message in context:
http://www.nabble.com/prefix-query-search-problem-if-a-hyphen-exist-in-the-search-word-tf4880266.html#a13966231
Sent from the Lucene - Java Users mailing list archive at Nabbl
Actually, my mind kind of overloaded when I read the following from
the (2.1) javadoc
- Splits words at punctuation characters, removing punctuation.
However, a dot that's not followed by whitespace is considered part of a
token.
- Splits words at hyphens, unless there's a number in
Doron Cohen wrote:
From the StandardAnalyzer javacc grammar :
// floating point, serial, model numbers, ip addresses, etc.
// every other segment must have at least one digit
etc.
<#P: ("_"|"-"|"/"|"."|",") >
My understanding of this: a non-whitespace sequence is broken
at eithe
"Michael D. Curtin" <[EMAIL PROTECTED]> wrote on 07/06/2007 13:30:28:
> > I think it splits by hyphens unless the no-hyphen
> > part has digits, so:
> > np-pandock-a7
> > becomes
> > np
> > pandock-a7
> > This is for the indexing part.
>
> Wow! Do you know the thinking behind that, i.e. why
Doron Cohen wrote:
I think it splits by hyphens unless the no-hyphen
part has digits, so:
np-pandock-a7
becomes
np
pandock-a7
This is for the indexing part.
Wow! Do you know the thinking behind that, i.e. why a number in a
hyphenated expression prevents the split?
--MDC
Michael D. Curtin wrote:
> > Np-pandock-L1
> > Np-pandock-L2
>
> I'm not positive, but I think StandardAnalyzer splits this input at the
> hyphens. That is, it gives the terms "Np", "pandock", "1", "2", "L",
> "L1", and "L2", but NOT "Np-pandoc", etc.
I think it splits by hyphens unless the no-h
John Powers wrote:
Np-pandock
Np-pandock-1
Np-pandock-2
Np-pandock-L
Np-pandock-L1
Np-pandock-L2
I'm not positive, but I think StandardAnalyzer splits this input at the
hyphens. That is, it gives the terms "Np", "pandock", "1", "2", "L",
"L1", and "L2", but NOT "Np-pandoc", etc.
--MD
Hello
I've asked before on this issue, and I think I have more information
now.
I have in a lucene 1.4 index, some Field.Text fields stored.I've
been focusing on the one called "name"
In luke 0.7 , run on the command line from a jar, if I do a search for
Name:"np-pandock*" I ge
John Powers wrote:
Lucene 1.4 is what I use for the application and how I compile things
But in the help/about it says "null"
And I usually use the webstart, ya. But I've tried from a downloaded
jar as well. and I'm using java1.6 from sun
Ah, all is clear now. Luke will not work with Lucene <
lto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 4:22 PM
To: java-user@lucene.apache.org
Subject: Re: search problem/odd results
John Powers wrote:
> java.lang.NoSuchFieldException: IMPL
> at java.lang.Class.getDeclaredField(Unknown Source)
That's a strange one ... Which
John Powers wrote:
java.lang.NoSuchFieldException: IMPL
at java.lang.Class.getDeclaredField(Unknown Source)
That's a strange one ... Which version of Lucene are you using with Luke
(you can check this in Help -> About box, look for "Lucene version:").
Are you running this from Java We
)
at java.awt.EventDispatchThread.run(Unknown Source)
IMPL
-Original Message-
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 3:27 PM
To: java-user@lucene.apache.org
Subject: Re: search problem/odd results
On Wednesday 09 May 2007 16:17, John Powers wrote
On Wednesday 09 May 2007 16:17, John Powers wrote:
> Yes, it doesn't work. it gives an error modal dialog box that says
> "IMPL".
Is there a more useful error message when you start Luke from the command
line and try to open the index?
Regards
Daniel
--
http://www.danielnaber.de
---
Yes, it doesn't work. it gives an error modal dialog box that says
"IMPL".
-Original Message-
From: Daniel Naber [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 4:45 PM
To: java-user@lucene.apache.org
Subject: Re: search problem/odd results
On Tuesday 08 May 2
On Tuesday 08 May 2007 23:42, John Powers wrote:
> I've had problems with luke in the past not being able to read the
> files.
Just make sure you specify the directory, not the files when opening an
index with Luke. Also use the latest version (0.7).
Regards
Daniel
--
http://www.danielnaber
completely, that'd be fine. but it returns two.. why those
two?That's the part I'm not getting.
Thanks for your response...
-Original Message-
From: Erick Erickson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 1:47 PM
To: java-user@lucene.apache.org
Subject: Re:
First question: What analyzers are you using at index and search time?
Second question: Have you tried using query.toString() to see how
the query parses? If so, you should post the results.
Third question: Have you used Luke to examine your index, to see
what's actually in there (which may surp
I don't understand why I'm getting the results I'm getting.
If I search for "pandock*" I get 6 results
Np-pandock
Np-pandock-L
Np-pandock-1
Np-pandock-2
Np-pandock
Np-pandock-L1
If I search for np-pandock I get
Np-pandock
Np-pandock-L
If I search for pandock I get
Np-pandock
Have you used Luke to see what is actually in the index? Or written
some test cases for your analyzer to know that the appropriate tokens
are coming out of your analyzer?
Also, could you give more details about the filters you are using? I
am not familiar w/ ExactTokensConstructorFilter,
Dear all,
We are using a Unified Analyzer as the analyzer of Lucene so as to be
able to index and search Arabic and English documents as well.
Here is the code:
public TokenStream tokenStream(String FieldName, Reader reader)
{
switch(analysisMode) {
n XML interface and can
be accessed from any language.
Best regards,
-Graham
> -Original Message-
> From: Kapil Chhabra [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 15, 2007 11:43 PM
> To: java-user@lucene.apache.org
> Subject: Re: My Category Search Problem
>
> Hi Vi
Hi Vijay,
I have hit the same problem in the past and have evaluated various
techniques to solve the same.
1. Using the QueryFilter
The idea is to
a) create BitSets for each category once initially
b) run the search and extract the BitSet for the search results
c) Logically "AND" the re
Hi Lucene Users!
I've been playing around with dotLucene on a few projects since for about 4
months, and I've found Lucene to be exceptionally powerful, speedy and
thanks to LIA, really easy to use.
But I've hit a problem that I fear will pose a performance problem for our
architecture and Lu
Hi,
I am doing "field:text" kind of search using my own analyzer which behaves
like whitespaceanalyzer. Following are the code snippets for my own
whitespaceanalyzer and whitespacetokenizer.
// WhiteSpaceAnalyzerMaestro.java
package com.hewitt.itk.maestro.support.service.simplesearch;
import
: I have modified the tokenizer class by making it return characters in
: lower case.
there is really no reason to do this ... have your analyzer use the
WhitespaceTokenizer, wrapped in a LowerCaseFilter ... that will illiminate
some of your custom code, and perhaps some of your problems as well.
Thanks Erick.
On 10/27/06, Erick Erickson <[EMAIL PROTECTED]> wrote:
I'm not all that familiar with the remotesearcher stuff. But somewhere you
must open an indexreader. So wherever that code is, just close the index
reader (and anything that uses it, like Serachables(?)) and re-open it.
That
s
I'm not all that familiar with the remotesearcher stuff. But somewhere you
must open an indexreader. So wherever that code is, just close the index
reader (and anything that uses it, like Serachables(?)) and re-open it. That
should pick up your recent changes.
Of course, now would be a fine time
Thanks Erick for the information.
Actually I am using RemoteParallelMultiSearcher with 10 Search Servers, my
crawler program freequently add new documents in to all the Search Servers
in a distributed manner. So in this case, if I add a document in a
particular index, I need to restart the search
Yes, but you must close and re-open your SEARCHER. There are various schemes
for doing this based upon now expensive it is to open a new searcher and how
often you need to do it, but it's not built into Lucene AFAIK. It all
depends upon how quickly you have to see the results of your update.
Also
Hi,
I have a program to create a lucene index, and another program for searching
that index.
The Search program create an IndexSearcher object once in its constructor,
and I created a method doSearch to search the index. The doSearch method
uses the indexSearcher object to get the Hits.
My Inde
I guess that fixes the problem.
Thanx
--
View this message in context:
http://www.nabble.com/search-problem-t1506294.html#a4096490
Sent from the Lucene - Java Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
: Problem: while there is a hit, only the timestamp and ip of the very first
: line in the logfile are shown, but not the "matching" ip and timestamp later
: in the logfile. Any suggestions how to get to the "right entries" ?
It sounds like you are creating one Document per logfile, and then usin
25 apr 2006 kl. 17.54 skrev April06:
We indexed several logfiles which contain for example a timestamp,
an ip and
additional information (all defined as a field) all in one line.
A logfile itself contains many of these lines.
We used a BooleanQuery (timestamp / ip) to search for a ip betwe
: while there is a hit, only the timestamp and ip of the very first
line in the logfile are shown, but not the "matching" ip and timestamp later
in the logfile. Any suggestions how to get to the "right entries" ?
Thank you very much.
--
View this message in context:
http://www.nabbl
: Where can I see the example using HitCollector ?
if you mean examples of writing a HitCollector, then the javadocs for the
HitCollector class are a good place to start. As is the source code for
TopDocCollector and and TopFieldDocCollector.
If you mean an example of using a HitCollector when
1 - 100 of 119 matches
Mail list logo
