[infinispan-issues] [JBoss JIRA] Updated: (ISPN-625) Lucene Directory's methods length, filemodified, touch should return 0L instead of FileNotFoundException for unexistent files

[Galder Zamarreño (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-625:
----------------------------------

    Fix Version/s:     (was: 5.0.0.BETA1)


> Lucene Directory's methods length, filemodified, touch should return 0L instead of FileNotFoundException for unexistent files
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-625
>                 URL: https://issues.jboss.org/browse/ISPN-625
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.1.0.CR3
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>             Fix For: 4.1.0.Final
>
>
> Lucene appears to be inconsistent on this behaviour; the FSDirectory documents a FileNotfoundException but actually returns 0 while the RAMDirectory implements the FileNotfoundException but is totally synchronized,
> I assume the FSDirectory is more reliable in this case and we got a reported error about this, my rationale is that the race condition which FSDirectory can handle is never an issue in the synchronized blocks of RAMDirectory.
> Inspecting the code of Lucene, there appears to be no harm done in returning 0 for unexistend metadata.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira