From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: command line interface to chunkd, tabled Date: Sun, 08 Nov 2009 14:50:08 -0500 Message-ID: <4AF720F0.1090507@garzik.org> References: <4AF6812C.5070706@garzik.org> <20091108115418.7c230a1a@redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091108115418.7c230a1a@redhat.com> Sender: hail-devel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Pete Zaitcev Cc: Project Hail On 11/08/2009 01:54 PM, Pete Zaitcev wrote: > On Sun, 08 Nov 2009 03:28:28 -0500, Jeff Garzik wrote: > >> A command line client for chunkd, chcli, was just committed. It offers >> the ability to GET (dumps to stdout) and PUT (input from cmd line arg). > > I wonder how you square that with the recent move away from ASCII keys. We didn't move away from ASCII keys, we added support for non-ASCII-hexidecimal keys :) The chcli '-k' option enables command line use of fully binary keys. But just like every other key/value store out there, people often use printable strings as keys, because it's an easy model for them to use. So we enable that easy model, too. This is somewhat analagous to db_dump[1], where full binary I/O is supported... but because of common usage, the ability to load text databases is also present. In a different perspective, chunkd recently gained the ability to support arbitrary ASCII keys, too. Jeff [1] http://www.oracle.com/technology/documentation/berkeley-db/db/api_reference/C/db_load.html