cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-926) remove alternative RPC interface using Avro
Date Thu, 13 Jan 2011 17:41:48 GMT


Eric Evans updated CASSANDRA-926:

    Summary: remove alternative RPC interface using Avro  (was: implement alternative RPC
interface using Avro)

> remove alternative RPC interface using Avro
> -------------------------------------------
>                 Key: CASSANDRA-926
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>         Attachments: v1-0001-CASSANDRA-926-denormalize-avro-internode-rpc-schema.txt,
v1-0002-don-t-build-schema-for-rpc-interface.txt, v1-0003-remove-option-to-launch-avro-rpc-daemon.txt,
v1-0004-remove-avro-functional-tests.txt, v1-0005-remove-avro-rpc-source.txt, v1-0006-move-remaining-avro-records-to-hadoop-package.txt
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> *UPDATE: This ticket is now for the removal of the Avro interface, (see
for background).*
> Avro is data serialization and RPC framework similar to Thrift. It provides:
> * Rich data structures.
> * A compact, fast, binary data format.
> * A container file, to store persistent data.
> * Remote procedure call (RPC).
> * Simple integration with dynamic languages. Code generation is not required to read
or write data files nor to use or implement RPC protocols. Code generation as an optional
optimization, only worth implementing for statically typed languages. 
> Cassandra's Avro interface is being structured in a way that closely mirrors the existing
Thrift interface, both in terms of public facing API, and how it is implemented. GSOC students
interested in this task should begin by familiarizing themselves with Cassandra's Thrift service
> Note: This is a very large and long-running task so treat this as a meta-issue and add
sub-tasks and/or blocking issues as appropriate.

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

View raw message