-
Notifications
You must be signed in to change notification settings - Fork 441
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
Extended Attributes Support (SetXAttr, GetXAttr, ListXAttr) #2525
Comments
As mentioned in the description, the request here is to support basic set, get, list operations on extended attributes and the starting can be done with storing them in iNode and later the functionality can be extended to populating them to the storage layer if required. I can work on supporting these operations once the feature request is accepted. |
Thanks @bhawesh-khandelwal for the suggestion, I will discuss with the team and get back to you. |
Thanks @raj-prince for the response. |
@raj-prince A gentle reminder on this. Were you able to discuss it with the team? |
@bhawesh-khandelwal While we are discussing this internally, it would be really helpful if you can elaborate a bit more on your use-case for extended attributes. |
@sethiay Sure. Our usecase is basically that we would want to store some extended attributes of the file for the mount session. Please let me know in case any other information is required. |
@bhawesh-khandelwal can you please provide more details on this usecase/project from a workload perspective (ex: AI/ML training, backup, home share, analytical workload, etc)? Also, do you work with a GCP account team you can also pass this request to? |
@marcoa6 Our usecase involves writing to gcs using gcsfuse and then we do backups. From a workload perspective, it is a backup project. |
Describe the issue
GCSFuse does not support set and get extend attributes posix operations (SetXAttr, GetXAttr, ListXAttr) and throws
operation not supported
error for these. This can be very useful for many use cases such as storing filesystem metadata, custom application data etc.There had been another request raised for similar but slightly different use case where the ask was to copy the metadata in case it is available in the object to local.
The request here is to at least support the operations on extended attributes for the session. These attributes can be stored in the iNode and can be served from the iNode as well. This can be the starting point and later this functionality can be extended to pushing these attributes to the cloud as well.
System & Version (please complete the following information):
Steps to reproduce the behavior with following information:
Additional context
Attaching the error screenshot for reference:
SLO:
We strive to respond to all bug reports within 24 business hours provided the information mentioned above is included.
The text was updated successfully, but these errors were encountered: