[Mulgara-general] Lucene question

[Paul Gearon]

Hi David,

I never worked with the Lucene resolver, so I don't have a lot to  
contribute, but I do know one answer....

On Jun 17, 2008, at 9:29 AM, David Smith wrote:

> The Lucene resolver seems to work,  we're still learning how it's  
> intended to be used.
> Searching works ok, within what appears to be the way Lucene wants  
> to work
>
> But we have 2 issues:
>
> 1) deletes don't work,
>     we're getting an error "Lock obtain timed out" when we try to  
> delete.
>     Has anyone else observed this?

I've seen occasional errors with locks in Lucene, but it hasn't been  
consistent enough for me to track down. I believe it's been around for  
a long time. Given the nature of the problem, I'd say it's a race  
somewhere.

> 2) droping the model doesn;t delete the indexes
>     Is this by design?
>     (I could se this being the case if Mulgara was looking over the  
> shoulder of another app that uses Lucene... but it seems odd from an  
> all mulgara application)

Yes, it's by design. I believe the problems comes from trying to stay  
synced with transactions, especially when a reading object is kept  
open while writes continue to happen (the reading object is not  
permitted to change regardless of any writes).

Regards,
Paul Gearon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mulgara.org/pipermail/mulgara-general/attachments/20080619/d286ea2a/attachment.htm>