>
>
>> Barring this we (place where I work, Chango) will probably eventually fork
>> Cassandra to have a RESTful interface and use the Jetty async HTTP client to
>> connect to it. It's just ridiculous for us to have threads and associated
>> resources tied up on I/O-blocked operations.
>>
>
> We've
An asynchronous thrift client in Java would be something that we could
really use; I'm trying to get a sense of whether this async client is usable
with Cassandra at this point -- given that Cassandra typically bundles a
specific older Thrift version, would the technique described here work at
all
I personally would love to see Cassandra add the concept of a read-only
'proxy' node which acts like the embedded ready only mode (Java 'fat
client') but sits as a stand alone server. It would know the the entire ring
and watch Gossip and thus be able to direct requests to the most appropriate
node
Apr 5, 2010 at 1:08 PM, Paul Prescod wrote:
> On Mon, Apr 5, 2010 at 5:29 AM, Ryan Daum wrote:
> > It seems pretty clear to me that the full memcached protocol is not
> > appropriate for Cassandra. The question is whether some subset of it is
> of
> > any use to anybody. Th
It seems pretty clear to me that the full memcached protocol is not
appropriate for Cassandra. The question is whether some subset of it is of
any use to anybody. The only advantage I can see is that there are a large
number of clients out there that can speak it already; but any app that is
making
I'm the author/maintainer of jmemcached; I'd be willing to do this and it'd
be quite easy to do, but Cassandra is missing a number of things which would
make it so we could only support a subset of the memcache protocol. Memcache
has:
set-if-not-present ("add")
atomic increment / decrement
compare
nk/0.7
> proper.
>
>
>
> *From:* Ryan Daum [mailto:r...@thimbleware.com]
> *Sent:* Wednesday, March 31, 2010 11:49 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: expiring data out of Cassandra/time to live
>
>
>
> I was able to successfully merge this patch into
I was able to successfully merge this patch into the 0.6 branch a few weeks
ago by doing the following:
- Downloading the patch
- Checking out the trunk of Cassandra from github
- Rolling back (checking out) the git repo to the same date that the
patch was submitted to Jira
- Apply
o create one jar file required for my
> testing. Note hector has not been upgraded to v6.
>
> For version 6, I suspect that we can yank the dependences out the
> ant/pom.xml file to determine the runtime jars needed.
>
>
> Tom
>
> <http://github.com/rantav/hector&g
I know people have been successful embedding Cassandra, and I've seen code
for how to bootstrap it, but I'm wondering what people have done to manage
its 3rd party dependencies at build time? Especially for Maven projects,
Cassandra is highly uncooperative as a dependency, as many of its 3rd party
+1, I'd like to try this patch but am running into error: patch failed:
src/java/org/apache/cassandra/utils/FBUtilities.java:342
Alternatively, someone could create a github fork which incorporates this
patch?
Ryan
On Sat, Mar 13, 2010 at 3:36 PM, Jonathan Ellis wrote:
> since they are separat
11 matches
Mail list logo
