[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: admin web UI
From:       Ran Tavory <rantav () gmail ! com>
Date:       2010-05-10 5:59:22
Message-ID: v2ne4b4609b1005092259y75e48e1foeeba4d1666830bde () mail ! gmail ! com
[Download RAW message or body]


I created this, hope it fits your expectations
https://issues.apache.org/jira/browse/CASSANDRA-1068
patch is attached to the bug and ready for review

2010/5/7 Ted Zlatanov <tzz@lifelogs.com>

> On Fri, 7 May 2010 09:24:40 +0200 gabriele renzi <rff.rff@gmail.com>
> wrote:
>
> gr> On Thu, May 6, 2010 at 7:00 PM, Nathan McCall <nate@vervewireless.com>
> wrote:
> >> FYI - I asked a similar question in #cassandra-dev yesterday (based on
> >> this message thread actually) and was directed to this issue:
> >> https://issues.apache.org/jira/browse/CASSANDRA-754
>
> gr> Interesting, but it seems the objection is more on the geneal idea of
> gr> "multiple APIs are a pain to mantain" than on the idea of having a
> gr> simple way for plugging external components with a lifecycle.
> gr> Maybe there is still space for such a minor patch?
>
> gr> (Also, though I understand the reasoning "one API should be enough for
> gr> everyone and two is too much for us" I don't see why such an option
> gr> should be ruled out for third parties, but I guess other people have
> gr> already put more thought than me in this)
>
> I'm sure if Cassandra maintainers heard from other people besides myself
> in favor of multiple APIs they would be more likely to listen.  I've
> argued enough on that ticket.
>
> FWIW I would again contribute in that direction if there was a chance of
> acceptance and I am concerned about the operational risks of the Thrift
> API and with the state of the Avro API.
>
> Ted
>
>


[prev in list] [next in list] [prev in thread] [next in thread]