cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-754) Pluggable API with a simple HTTP+JSON daemon
Date Fri, 19 Feb 2010 20:36:28 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835941#action_12835941
] 

Eric Evans commented on CASSANDRA-754:
--------------------------------------

> The Thrift HTTP+JSON server is an interesting possibility here, it could coexist with
the regular Thrift service and still serve the same API. Anyone interested in producing a
patch? Or I could put one together...

So having gone through the discussion and arriving where we are now, I can 't see how exposing
multiple combinations of transports and encodings from a framework already in use is any different
than supporting similar combinations via a pluggable API, the end result is the same, no?

What problem are we trying to solve that can't be solved by a single remote API? Or is it
that Thrift and/or Avro with a binary encoding is the wrong choice for the One True API and
JSON is the right one?

If I'm being honest, I'm not at all interested in committing a change like this myself, regardless
of how it is implemented, and more and more I'm leaning toward an outright veto (not something
I would do lightly). 

I am still open to the idea that I'm wrong about this, I just haven't yet heard a compelling
argument.

> Pluggable API with a simple HTTP+JSON daemon
> --------------------------------------------
>
>                 Key: CASSANDRA-754
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-754
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Ted Zlatanov
>            Assignee: Ted Zlatanov
>            Priority: Minor
>         Attachments: 0001-renamed-API-classes.patch, 0002-renamed-Avro-API-classes.patch,
0003-renamed-daemon-classes.patch, 0004-API-top-level-support.patch, 0005-adjust-references-to-point-to-new-API-classes.patch,
0006-adjust-Hadoop-and-tests.patch, v2-0001-CASSANDRA-754-use-less-specific-descriptors-for-Thrift.txt,
v2-0002-start-avro-daemon-using-a-arg-to-startup-script.txt
>
>
> Proposal of a simple pluggable API interface with a HTTP daemon implementation

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message