[
https://issues.apache.org/jira/browse/ARROW-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Moritz updated ARROW-4217:
----------------------------------
Description:
Currently, Plasma supports custom metadata for objects. This doesn't seem to be
used at the moment, and removing it will simplify the interface and
implementation of plasma. Removing the custom metadata will also make eviction
to other blob stores easier (most other stores don't support custom metadata).
My personal use case was to store arrow schemata in there, but they are now
stored as part of the object itself.
If nobody else is using this, I'd suggest removing it. If people really want
metadata, they could always store it as a separate object if desired.
was:
Currently, Plasma supports custom metadata for objects. This doesn't seem to be
used at the moment, and it will simplify the interface and implementation to
remove it. Removing the custom metadata will also make eviction to other blob
stores easier (most other stores don't support custom metadata).
My personal use case was to store arrow schemata in there, but they are now
stored as part of the object itself.
If nobody else is using this, I'd suggest removing it. If people really want
metadata, they could always store it as a separate object if desired.
> [Plasma] Remove custom object metadata
> --------------------------------------
>
> Key: ARROW-4217
> URL: https://issues.apache.org/jira/browse/ARROW-4217
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Plasma (C++)
> Affects Versions: 0.11.1
> Reporter: Philipp Moritz
> Assignee: Philipp Moritz
> Priority: Minor
> Fix For: 0.13.0
>
>
> Currently, Plasma supports custom metadata for objects. This doesn't seem to
> be used at the moment, and removing it will simplify the interface and
> implementation of plasma. Removing the custom metadata will also make
> eviction to other blob stores easier (most other stores don't support custom
> metadata).
> My personal use case was to store arrow schemata in there, but they are now
> stored as part of the object itself.
> If nobody else is using this, I'd suggest removing it. If people really want
> metadata, they could always store it as a separate object if desired.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
