Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Support Fileset on JuiceFS #5576

Open
caican00 opened this issue Nov 14, 2024 · 4 comments
Open

[FEATURE] Support Fileset on JuiceFS #5576

caican00 opened this issue Nov 14, 2024 · 4 comments
Labels
feature New feature or request

Comments

@caican00
Copy link
Collaborator

Describe the feature

Support Fileset on JuiceFS

Motivation

No response

Describe the solution

No response

Additional context

No response

@caican00 caican00 added the feature New feature or request label Nov 14, 2024
@YxAc
Copy link
Contributor

YxAc commented Nov 14, 2024

Are you looking to utilize fuse of JuiceFS?

I believe we can support two approaches simultaneously: one is the native fuse of GVFS (which is track in #5504 ), and the other is to reuse the fuse from JuiceFS.

what do you think? @diqiu50 @jerryshao

@diqiu50
Copy link
Contributor

diqiu50 commented Nov 18, 2024

That's OK.
Does this mean that the fileset only provides the JuiceFS path to be mounted, while the mounting operation is handled by another script or program, or is it executed by the Gravitino VFS?

@caican00
Copy link
Collaborator Author

caican00 commented Nov 18, 2024

Does this mean that the fileset only provides the JuiceFS path to be mounted

yes, It can be understood this way.

while the mounting operation is handled by another script or program, or is it executed by the Gravitino VFS?

It seems more reasonable to provide a unified mount interface, which can be implemented by native fuse or juiceFS fuse, and the users can use a config to specify which one they want to use.

WDYT? cc @diqiu50

@diqiu50
Copy link
Contributor

diqiu50 commented Nov 19, 2024

If we only provide the JuiceFS mount path, adding an interface to GVFS would suffice.
However, if we aim for unified mounting in GVFS, reference to the issue #5504

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants