[ 
https://issues.apache.org/jira/browse/LUCENE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577220#action_12577220
 ] 

Mark Miller commented on LUCENE-1214:
-------------------------------------

I am still trying to work that out...some craziness that started after I 
updated Lucene to trunk, but also made other fundamental changes, and windows 
vista may be haunting me too...

The gist of it is that Lucene is failing when it tries to create an index file 
(creates the directory fine). I don't think its Lucene related at the moment, 
but I havnt gotten to the bottom of it either.

Oddly, if I stop using the NoLockFactory (I manually manage a single Writer), 
things work...still digging though.

> Possible hidden exception on SegmentInfos commit
> ------------------------------------------------
>
>                 Key: LUCENE-1214
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1214
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3.1
>            Reporter: Mark Miller
>            Assignee: Michael McCandless
>            Priority: Trivial
>         Attachments: LUCENE-1214.patch
>
>
> I am not sure if this is that big of a deal, but I just ran into it and 
> thought I might mention it.
> SegmentInfos.commit removes the Segments File if it hits an exception. If it 
> cannot remove the Segments file (because its not there or on Windows 
> something has a hold of it), another Exception is thrown about not being able 
> to delete the Segments file. Because of this, you lose the first exception, 
> which might have useful info, including why the segments file might not be 
> there to delete.
> - Mark

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to