You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently , all Gravitino File system providers use the following code
(Take HDFSFileSystemProvider for example)
FileSystem.instance will always create a new Filesystem everytime even though they are the same mostly. In fact Hadoop FileSystem did have cache mechanism, If we use FileSystem.get, cache mechanism in FileSystem will works. Due to the fact the Gravitino virtual FileSystem (GVFS) client also shares FileSystemProviders and supports credentials for each unique path, we should be cautious when planning to enable cache in the file system. in all
In Gravitno server side, we can enable cache in FileSystem level
In GVFS, we need to disable it FileSystem level and cache file system instacen in GVFS level
The text was updated successfully, but these errors were encountered:
Currently , all Gravitino File system providers use the following code
(Take HDFSFileSystemProvider for example)
FileSystem.instance
will always create a new Filesystem everytime even though they are the same mostly. In fact Hadoop FileSystem did have cache mechanism, If we useFileSystem.get
, cache mechanism in FileSystem will works. Due to the fact the Gravitino virtual FileSystem (GVFS) client also shares FileSystemProviders and supports credentials for each unique path, we should be cautious when planning to enable cache in the file system. in allThe text was updated successfully, but these errors were encountered: