This us great! Are you going to put some functional and design docs
on the Wiki? This seems pretty important to get right and could save
you a lot of time getting feedback from the community on your overall
approach.
Just for example, a discussion of your hashing mechanism would be
great, and how you handle repartitioning on node failure, etc.
Thanks!
David
------------------
David Van Couvering
http://davidvancouvering.blogspot.com
On Feb 26, 2009, at 2:04 PM, Ben Browning <ben...@gmail.com> wrote:
I'm actively interested in getting two of the things you mentioned,
partitioning of data and a single view of the cluster, developed and
working. I haven't said much about the subject since the thread Jan
mentioned but I've been thinking a lot of things over in my head and
have an attack plan.
My first goal is to create an Erlang API which will probably be a
subset of the current HTTP API. I've seen this requested before on the
mailing list and believe this is a necessary first step to getting
partitioning support. After that I plan to tackle the actual
partitioning. I'll be doing all development in the following github
fork:
http://github.com/bbrowning/couchdb/tree/master
There are no changes there yet but you should start seeing code pop up
this week. At various points along the process I'll explicitly solicit
feedback from the devs and the rest of the community since my hope is
this code will eventually be used for partitioning in CouchDB proper.
I can't speak for the priority of this in the community, but it's the
only piece of Couch I'm currently working on and am planning to devote
at least 10-20 hours a week to it.
Ben
On Thu, Feb 26, 2009 at 12:53 PM, Jan Lehnardt <j...@apache.org> wrote:
That is about correct, see the current (slightly stale) thread
"Partitioned Clusters"* on the dev@ mailing list.
* Started by Chris Anderson on February 20th.
