zhengsg commented on issue #5763:
URL: https://github.com/apache/gravitino/issues/5763#issuecomment-2520216270

   > > > Alluxio supports 
HCFS(https://docs.alluxio.io/os/user/stable/en/api/Java-API.html#hadoop-compatible-java-client),
 which also supports by the Fileset, so I think you could refer to the 
implementations for Fileset managing the cloud storages in Gravitino to support 
Alluxio. Do you have any interest to contribute it?
   > > 
   > > 
   > > Thank you for your response. I’m not trying to contribute a solution in 
this area, I just want to know if there are any plans within the community to 
support Alluxio, or how the community views the overlapping functionality 
between the GVFS virtual file protocol and Alluxio’s file proxy protocol. 
Additionally, I’d like to know if there are any plans for GVFS to offer a file 
caching feature in the future, so that users adopting Alluxio could potentially 
switch to GVFS as an alternative.
   > 
   > Sorry, as far as I know, the community has no plans to support Alluxio, 
but I think it would be a good extension point. The current design of Fileset 
GVFS is very lightweight. The current goal is to manage non-table resources in 
Gravitino in the form of Fileset and read and write through a unified client. I 
think it is not a simple task to support file caching in GVFS. Why not consider 
managing Alluxio resources under Fileset, so as to reuse Alluxio's caching 
capabilities and let Alluxio shield the differences between various storages?
   
   I am considering using Alluxio's file system as a type of fileset management 
for Gravtino through the custom fileset extension provided by the community, 
which would allow for the reuse of Alluxio's caching capabilities. I just 
wanted to consult the community’s perspective on this and see if there are any 
plans in this area. Also, I haven’t seen the overall roadmap for Gravtino yet. 
Could you please provide some insight on that?


-- 
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]

Reply via email to