lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mathieu Lecarme <math...@garambrogne.net>
Subject Re: 答复: 答复: Lucene in large database contexts
Date Sat, 11 Aug 2007 17:15:47 GMT
With Compass, indexing is linked to your database transaction, when  
your object is persisted, it's indexed too.
All your questions are managed cleanly and silently by Compass, just  
have a look to the source code if you don't wont to use this product.

M.

Le 10 août 07 à 12:24, Antonello Provenzano a écrit :

> Kai,
>
> The context I'm going to work with requires a continuous addition of
> documents to the indexes, since it's user-driven content, and this
> would require the content to be always up-to-date.
> This is the problem I'm facing, since I cannot rebuild a 1Gb (at
> least) index every time a user inserts a new entry into the database.
>
> I know Digg, for instance, is using Lucene as search engine: since the
> amount of data they're dealing with is much higher than mine, I would
> like to understand the way they used to implement this kind of
> solution.
>
> Thank you again.
> Antonello
>
>
> On 8/10/07, Kai Hu <kai.hu@dusee.cn> wrote:
>> Antonello,
>>         You are right,I think lucene indexsearcher will search the  
>> old information if IndexWriter was not closed(I think lucene  
>> release the Lock here),so I only add a few documents every time  
>> from buffer to implement index "real time".
>>
>> kai
>>
>>
>> 发件人: antonelloprov@gmail.com  
>> [mailto:antonelloprov@gmail.com] 代表 Antonello Provenzano
>> 发送时间: 2007年8月10日 星期五 17:59
>> 收件人: java-user@lucene.apache.org
>> 主题: Re: 答复: Lucene in large database contexts
>>
>> Kai,
>>
>> Thanks. The problem I see it's that although I can add a Document
>> through IndexWriter or IndexModifier, this won't be searchable until
>> the index is closed and, possibly, optimized, since the score of the
>> document in the index context must be re-calculated on the basis of
>> the whole context.
>>
>> Is this assumption true? or am I completely wrong?
>>
>> Cheers.
>> Antonello
>>
>>
>> On 8/10/07, Kai Hu <kai.hu@dusee.cn> wrote:
>>> Hi, Antonello
>>>         You can use IndexWriter.addDocument(Document document) to  
>>> add single document,same to update,delete operation.
>>>
>>> kai
>>>
>>> -----邮件原件-----
>>> 发件人: Antonello Provenzano [mailto:antonelloprov@gmail.com]
>>> 发送时间: 2007年8月10日 星期五 17:09
>>> 收件人: java-user@lucene.apache.org
>>> 主题: Lucene in large database contexts
>>>
>>> Hi There!
>>>
>>> I've been working for a while on the implementation of a website
>>> oriented to contents that would contain millions of entries, most of
>>> them indexable (such as descriptions, texts, names, etc.).
>>> The ideal solution to make them searchable would be to use Lucene as
>>> index and search engine.
>>>
>>> The reason I'm posting the mailing list is the following: since all
>>> the entries will be stored in a database (most likely MySQL  
>>> InnoDB or
>>> Oracle), what's the best technique to implement a system that  
>>> indexes
>>> in "real time" (eg. when an entry is inserted into the databsse) the
>>> content and make it searchable? Based on my understanding of Lucene,
>>> such this thing is not possible, since the index must be re- 
>>> created to
>>> be able to search the indexed contents. Is this true?
>>>
>>> Eventually, could anyone point me to a working example about how to
>>> implement such a similar context?
>>>
>>>
>>> Thank you for the support.
>>> Antonello
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message