You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2020/09/23 15:30:00 UTC
[jira] [Updated] (ARROW-4217) [Plasma] Remove custom object
metadata
[ https://issues.apache.org/jira/browse/ARROW-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krisztian Szucs updated ARROW-4217:
-----------------------------------
Fix Version/s: (was: 2.0.0)
3.0.0
> [Plasma] Remove custom object metadata
> --------------------------------------
>
> Key: ARROW-4217
> URL: https://issues.apache.org/jira/browse/ARROW-4217
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++ - Plasma
> Affects Versions: 0.11.1
> Reporter: Philipp Moritz
> Assignee: Philipp Moritz
> Priority: Minor
> Fix For: 3.0.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
(v8.3.4#803005)