All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail <hail-devel@vger.kernel.org>
Subject: Re: command line interface to chunkd, tabled
Date: Sun, 08 Nov 2009 14:50:08 -0500	[thread overview]
Message-ID: <4AF720F0.1090507@garzik.org> (raw)
In-Reply-To: <20091108115418.7c230a1a@redhat.com>

On 11/08/2009 01:54 PM, Pete Zaitcev wrote:
> On Sun, 08 Nov 2009 03:28:28 -0500, Jeff Garzik<jeff@garzik.org>  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

      reply	other threads:[~2009-11-08 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08  8:28 command line interface to chunkd, tabled Jeff Garzik
2009-11-08 18:54 ` Pete Zaitcev
2009-11-08 19:50   ` Jeff Garzik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF720F0.1090507@garzik.org \
    --to=jeff@garzik.org \
    --cc=hail-devel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.