From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: hail-devel@vger.kernel.org
Subject: Re: [PATCH] chunkd: add cp command, for local intra-table copies
Date: Tue, 06 Jul 2010 15:42:22 -0400 [thread overview]
Message-ID: <4C33871E.7080203@garzik.org> (raw)
In-Reply-To: <20100706091730.67ebdfee@lembas.zaitcev.lan>
On 07/06/2010 11:17 AM, Pete Zaitcev wrote:
> On Tue, 6 Jul 2010 03:24:29 -0400
> Jeff Garzik<jeff@garzik.org> wrote:
>
>> The following patch, against current hail.git, adds the "CP" command to
>> chunkd, permitting copying from object->object inside a single table.
>
> What is it for?
Here's a real-world example.
Quoting from the S3 documentation, this describes the "PUT (copy)"
operation, something that tabled does not yet support, but should:
This implementation of the PUT operation creates a copy of an
object that is already stored in Amazon S3. A PUT copy
operation is the same as performing a GET and then a PUT.
Adding the request header, x-amz-copy-source, makes the PUT
operation copy the source object into the destination bucket.
Assuming that a given tabled object is already fully replicated --
HOPEFULLY the common case for us -- the least expensive way to implement
this is
for each chunkd containing object OLD_KEY
CHO_CP(object OLD_KEY -> object NEW_KEY)
Assuming each chunkd node has the necessary free space, this method
totally avoids using network bandwidth, when creating a copy of an object
Jeff
prev parent reply other threads:[~2010-07-06 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 7:24 [PATCH] chunkd: add cp command, for local intra-table copies Jeff Garzik
2010-07-06 15:17 ` Pete Zaitcev
2010-07-06 16:59 ` Jeff Garzik
2010-07-06 19:42 ` 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=4C33871E.7080203@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.