Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <u2g8211a1321004151835y37703344zbd86e66a8d7fa708@mail.gmail.com>
References: <n2u50db8f51004141842i3d7b4637y1f8c1f2a3abcba32@mail.gmail.com>
	 <q2p5f7770581004141908ge4ac882gcdfede9ad845fc6@mail.gmail.com>
	 <g2z50db8f51004141915g5111345r7245e40ca00d1e58@mail.gmail.com>
	 <n2ua06de5521004141925q7f33688ag95f0341b38134dd3@mail.gmail.com>
	 <k2ka06de5521004141926j57955f97of9259ca62500545@mail.gmail.com>
	 <s2zda04fdf51004141932ze51d5c3av461f762afdf6f3b8@mail.gmail.com>
	 <t2o8211a1321004141936of5c4520ds6d8e24db77dfd049@mail.gmail.com>
	 <z2le06563881004142050ybd1f6b6bvaa7378258e2b06d0@mail.gmail.com>
	 <u2g8211a1321004151835y37703344zbd86e66a8d7fa708@mail.gmail.com>
Date: Thu, 15 Apr 2010 21:04:23 -0700
Message-ID: <l2wa17e13e71004152104ve531a180x5ccbfafcd017b86c@mail.gmail.com>
Subject: Re: Is that possible to write a file system over Cassandra?
From: Nathan McCall <nate@vervewireless.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

In regards to hector, please check all the available branches on
github. We have supported 0.6 for a little while now.

http://github.com/rantav/hector/tree/0.6.0

The master is still based on 0.5, but that is changing in the next
couple of days to match the 0.6 release.

-Nate


On Thu, Apr 15, 2010 at 6:35 PM, Jeff Zhang <zjffdu@gmail.com> wrote:
> Jonathan,
>
> Previously we use the cassandra-0.6, but we'd like to leverage the hector
> java client since it has more advanced features. And hector currently onl=
y
> support cassandra-0.5.
> Why you think using casandra-0.5 is a stange way to do it ? Is cassandra-=
0.6
> incompatibility with cassandra-0.5 ? The migration to cassandra-0.6 will
> cost much ?
>
>
> On Thu, Apr 15, 2010 at 11:50 AM, Jonathan Ellis <jbellis@gmail.com> wrot=
e:
>>
>> You forked Cassandra 0.5 for that?
>>
>> That's... a strange way to do it.
>>
>> On Wed, Apr 14, 2010 at 9:36 PM, Jeff Zhang <zjffdu@gmail.com> wrote:
>> > We are currently doing such things, and now we are still at the start
>> > stage.
>> > Currently we only plan to store small files. For large files, splittin=
g
>> > to
>> > small blocks is really one of our options.
>> > You can check out from here http://code.google.com/p/cassandra-fs/
>> >
>> > Document for this project is lack now, but still welcome any feedback
>> > and
>> > contribution.
>> >
>> >
>> >
>> > On Wed, Apr 14, 2010 at 7:32 PM, Miguel Verde <miguelitovert@gmail.com=
>
>> > wrote:
>> >>
>> >> On Wed, Apr 14, 2010 at 9:26 PM, Avinash Lakshman
>> >> <avinash.lakshman@gmail.com> wrote:
>> >>>
>> >>> OPP is not required here. You would be better off using a Random
>> >>> partitioner because you want to get a random distribution of the
>> >>> metadata.
>> >>
>> >>
>> >> Not required, certainly.=A0 However, it strikes me that 1 cluster is
>> >> better
>> >> than 2, and most consumers of a filesystem would expect to be able to
>> >> get an
>> >> ordered listing or tree of the metadata which is easy using the OPP r=
ow
>> >> key
>> >> pattern listed previously.=A0 You could still do this=A0with the Rand=
om
>> >> partitioner using=A0column names in rows to describe the structure bu=
t
>> >> the
>> >> current compaction limitations could be an issue if a branch becomes
>> >> too
>> >> large, and you'd still have a root row hotspot (at least in the schem=
a
>> >> which
>> >> comes to mind).
>> >
>> >
>> > --
>> > Best Regards
>> >
>> > Jeff Zhang
>> >
>
>
>
> --
> Best Regards
>
> Jeff Zhang
>