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
Some engines like Tensorflow may create the GravitinoVirtualFilesystem, and pass the path that does not have the scheme prefix.
In the current implementation, the path has to set the scheme prefix, it will not work with TensorFlow. In the issue, we will improve it.
Tensorflow will parseHadoopPath after creating the HadoopFileSystem(GravitinoVirtualFIleSystem). After that, it will use the path that has no scheme prefix to invoke API.
What would you like to be improved?
Some engines like Tensorflow may create the GravitinoVirtualFilesystem, and pass the path that does not have the scheme prefix.
In the current implementation, the path has to set the scheme prefix, it will not work with TensorFlow. In the issue, we will improve it.
Tensorflow will parseHadoopPath after creating the HadoopFileSystem(GravitinoVirtualFIleSystem). After that, it will use the path that has no scheme prefix to invoke API.
How should we improve?
improve the compatibility to support the path with scheme prefix and the path without scheme prefix
The text was updated successfully, but these errors were encountered: