From 42878d7b94e04d5a6eaf502c4fd775a1adaa0ecf Mon Sep 17 00:00:00 2001 From: Nicola Coretti Date: Wed, 20 Mar 2024 11:50:00 +0100 Subject: [PATCH] Update doc/design/bucketpath.rst Co-authored-by: Christoph Kuhnke --- doc/design/bucketpath.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/bucketpath.rst b/doc/design/bucketpath.rst index 1dcd50cb..9072d021 100644 --- a/doc/design/bucketpath.rst +++ b/doc/design/bucketpath.rst @@ -20,7 +20,7 @@ Challenges with Current BucketFS Interactions +++++++++++++++++++++++++++++++++++++++++++++ 1. **Contextual Versatility:** - Users face difficulties when switching between different operational contexts, such as external access (http) versus internal access (local pahts, during UDF execution). The lack of a seamless transition between contexts hinders productivity and introduces additonal code complexities. + Users face difficulties when switching between different operational contexts, such as external access (HTTP) versus internal access (local paths, during UDF execution). The lack of a seamless transition between contexts hinders productivity and introduces additonal code complexities. 2. **Directory Operations:** BucketFS inherently lacks the concept of directories as understood in traditional file systems. This absence complicates tasks like listing directory contents, making what should be simple actions cumbersome and time-consuming. Users are forced to interact with a lower-level bucket API for directory-like operations, which is not only tedious but also counterintuitive.