-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Sprint 79, Sprint 80
-
2
Currently, when a file is first opened its location is cached. Consider:
- open F1 read-only
- open F2 write-only
The second operation would lookup the cached location in MetadataCache and reuse the "read-only" location, foregoing permission checks (GetFileLocation and GetNewFileLocation are threated as open in cluster) and potentially trying to write to a read-only storage.