Include object metadata in container list

Bug #1319096 reported by Robin Winslow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Won't Fix
Undecided
Unassigned

Bug Description

Would it be possible to include the contents of any arbitrary meta header values (X-Object-Meta-*) in the data returned when querying a container?

As per this ask question: https://ask.openstack.org/en/question/29563/swift-meta-data-of-all-objects-in-a-container/

tags: added: container
removed: containers
Changed in swift:
status: New → In Progress
Revision history for this message
Janie Richling (jrichli) wrote :

Hello Christian. This would be nice information to have. The challenge is that user metadata for objects is not stored in the container DB, and adding such support would not be appropriate use of the container DB. The object servers are the part of swift that is scaled to hold all the data for objects. Futhermore, accessing the data from the object servers for all objects in the container is not performant for a container listing. What are your thoughts on how to implement this?

Revision history for this message
Alistair Coles (alistair-coles) wrote :

Agree with Janie. I'd also note that it will be a major challenge to have the consistency engine maintain consistent updateable* object metadata state in container db's if it were to be added. There is currently one item of updateable object metadata in the container db, i.e. Content-Type, and that was a major pain when fixing object (fast) POST support. I would advocate that we do not add any more updateable metadata to the container rows.

* by updateable I mean it can be modified by a POST

Tim Burke (1-tim-z)
tags: added: container-listings
Revision history for this message
Thiago da Silva (thiagodasilva) wrote :

I'm tempted to close this bug as 'Won't Fix', any objections? Given what Janie and Alistair already explained, object metadata is stored with objects not on container servers, querying every object of a container to get metadata would kill performance and storing object metadata on containers db is also a no-go.

Revision history for this message
Thiago da Silva (thiagodasilva) wrote :

Please feel free to re-open if I'm missing something...

Changed in swift:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.