cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-342) hadoop integration
Date Fri, 21 Aug 2009 15:54:14 GMT


Stu Hood commented on CASSANDRA-342:

Since the Hadoop InputFormat can't possibly be in the same process as the Cassandra server
on the local machine, perhaps the cleanest interface between them would be a 'private' client
library (not using Thrift) that allows for the calls you need? The only call I see to an internal
API is StorageService.getRangeToEndPointMap, so we could add a Verb that queries a remote/local
running node for the same information.

It doesn't look like it would be too difficult to extract just the net.MessagingService portion
of the Cassandra server, and then use that as the private client interface to send messages
to other nodes.

> hadoop integration
> ------------------
>                 Key: CASSANDRA-342
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>         Attachments: 0001-CASSANDRA-342.-Set-up-for-the-hadoop-commits.patch, 0001-the-stupid-version-of-hadoop-support.patch,
0001-v3-CASSANDRA-342.-Set-up-for-the-hadoop-commits.patch, 0002-CASSANDRA-342.-Working-hadoop-support.patch,
0002-v3-CASSANDRA-342.-Working-hadoop-support.patch, 0003-CASSANDRA-342.-Adding-the-WordCount-example.patch,
0003-v3-CASSANDRA-342.-Adding-the-WordCount-example.patch, v2-squashed-commits-for-hadoop-stupid.patch
> Some discussion on -dev:

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

View raw message