Open Stack

On Thu, Jan 24 2013, Lu, Lianhao wrote:

> One thing concerns me is that it can only handle the first level key/pair
> in metadata. What about the other level keypair, e.g. {"key3": {"key31": 31}}?
> Should we flatten the metadata into {"key3.key31": 31} and store that into the
> metadata table? 

I'm not sure there's counters using nested metadata, and I'm pretty sure
there's nothing that couldn't be nested.

> Or should we put some restriction on the metadata that it must be key/value
> dict, in which the value could only be sting/int/float or another dict abiding the same
> rules?

Yes, I don't think putting restrictions on that is a huge problem.

-- 
Julien Danjou
# Free Software hacker & freelance
# http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130124/5f901ce1/attachment.pgp>