Re: json, binary data, and ceph config-key

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18-04-10 05:59 AM, Patrick Donnelly wrote:
On Mon, Apr 9, 2018 at 8:39 PM, Sage Weil <sweil@xxxxxxxxxx> wrote:
Should we

[..]

All of these options kind of suck.  Is there a better option I'm missing?

[..]

Or, (6) output values as

     "config-history/1/": {
       "type": "string",
       "value": "bar"
     },
     "config-history/1/": {
       "type": "blob",
       "value": "base64://ABCD=="
     }
     "config-history/2/": {
       "type": "integer",
       "value": 1
     }

(Perhaps a last minute change to add blobs or maybe just dynamically
recognize them.)

+1 for that - add "blob" type that's always base64 or base85 (https://en.wikipedia.org/wiki/Ascii85) encoded and use it for values that may contain binary data - it isn't human-readable anyway.

--
Piotr Dałek
piotr.dalek@xxxxxxxxxxxx
https://www.ovh.com/us/
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux