From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH] chunkd: update backend to support binary keys
Date: Wed, 04 Nov 2009 01:26:50 -0500
Message-ID: <4AF11EAA.6090302@garzik.org>
References: <20091104055137.GA17995@havoc.gtf.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
In-Reply-To: <20091104055137.GA17995@havoc.gtf.org>
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: hail-devel@vger.kernel.org

On 11/04/2009 12:51 AM, Jeff Garzik wrote:
>
> (yeah, the summary line needs s/cld:/chunkd:/)
>
>
> Just committed the following change to chunkd's storage backend API,
> preparing chunkd for variable-length opaque binary keys.
>
>
>
> commit 0a8c3225355de86484eba71279c646f7790d5bb1
> Author: Jeff Garzik<jeff@garzik.org>
> Date:   Wed Nov 4 00:44:55 2009 -0500
>
>      cld: update storage backend to store based on opaque binary key + key length
>
>      Change internal structure to utilize an opaque binary key, rather than the
>      existing probably-nul-terminated, fixed length C hexidecimal string key.
>
>      Storage backend now names files based on the SHA256 of the key.
>
>      The key, in its entirety, is written to each object's header in the
>      filesystem, to assist in recovery.


To emphasize, this is a chunkd on-disk database format change.

	Jeff