tustvold opened a new issue, #4754:
URL: https://github.com/apache/arrow-rs/issues/4754
_This is a draft proposal, and likely needs more polish_
**Is your feature request related to a problem or challenge? Please describe
what you are trying to do.**
<!--
A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
(This section helps Arrow developers understand the context and *why* for
this feature, in addition to the *what*)
-->
Many stores provide the ability to associate arbitrary user-defined
attributes with objects, it would be useful to expose this.
**Describe the solution you'd like**
<!--
A clear and concise description of what you want to happen.
-->
I would like to propose a new `put_opts` call, in a similar vein to the
existing `get_opts`. This would take a `PutOptions`
```
pub struct PutOptions {
pub metadata: HashMap<String, String>
}
```
Stores that can't store metadata should return an error if passed metadata,
and `ObjectMeta` should be updated to include such metadata.
Unix systems can likely make use of [xattr](https://crates.io/crates/xattr)
to store user metadata
We will likely need to restrict the key names in some manner
**Describe alternatives you've considered**
<!--
A clear and concise description of any alternative solutions or features
you've considered.
-->
**Additional context**
<!--
Add any other context or screenshots about the feature request here.
-->
https://github.com/apache/arrow-rs/issues/4498 also calls for some sort of
put_opts style API
https://github.com/apache/arrow-rs/issues/4753 would benefit from this
functionality
--
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]
