felipecrv commented on issue #40037: URL: https://github.com/apache/arrow/issues/40037#issuecomment-1938789428
> Its possible that a user of the AzureFileSystem might accidentally try to read or write a directory marker which could cause confusion. Can you clarify the sequence that leads to the confusion? I think we should aim for having no confusion if the user writes to Azure Storage only via the `arrow::FileSystem` API and fail-fast on confusion created by other writers. For example, I agree we shouldn't allow creation of files that get the same name as a directory (including implied directories [when a marker doesn't exist, but some blob exists with that directory as a path-prefix]). > On flat namespace accounts we ensure that directory marker blobs always have a trailing / and files never have a trailing /. This prevents accidentally reading or writing a directory marker blob but it also allows creating a file and a directory with exactly the same name, which seems to cause significant problems for GetFileInfo. @felipecrv do you have any thoughts on this? I think we can figure cheap ways (with at most one extra request) to check against this. Preventing file open with paths containing trailing slashes is a good start because it will catch most of the times this would happen in practice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
