cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6846) Provide standard interface for deep application server integration
Date Sat, 15 Mar 2014 14:30:45 GMT


Edward Capriolo commented on CASSANDRA-6846:

To facilitate deep server integrations users should be able to bring up other things easily
with the start of cassandra. For example I have patched in a second thrift server here:

Theoretically this could be anything, tomcat, jetty, storm, a mail server, who knows. Currently
the yaml file has options to enable disable thrift/native. This is not flexible enough. the
enabled deamons should be a list of class names and the user should be able to plug whatever
they wish into said list. If these things need to be configured that should not be done in
the cassandra.yaml but through separate configuration files.

> Provide standard interface for deep application server integration
> ------------------------------------------------------------------
>                 Key: CASSANDRA-6846
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Tupshin Harper
>            Assignee: Tupshin Harper
>            Priority: Minor
>              Labels: ponies
> Instead of creating a pluggable interface for Thrift, I'd like to create a pluggable
interface for arbitrary app-server deep integration.
> Inspired by both the existence of intravert-ug, as well as there being a long history
of various parties embedding tomcat or jetty servlet engines inside Cassandra, I'd like to
propose the creation an internal somewhat stable (versioned?) interface that could allow any
app server to achieve deep integration with Cassandra, and as a result, these servers could

> 1) host their own apis (REST, for example
> 2) extend core functionality by having limited (see triggers and wide row scanners) access
to the internals of cassandra
> The hand wavey part comes because while I have been mulling this about for a while, I
have not spent any significant time into looking at the actual surface area of intravert-ug's
integration. But, using it as a model, and also keeping in minds the general needs of your
more traditional servlet/j2ee containers, I believe we could come up with a reasonable interface
to allow any jvm app server to be integrated and maintained in or out of the Cassandra tree.
> This would satisfy the needs that many of us (Both Ed and I, for example) to have a much
greater degree of control over server side execution, and to be able to start building much
more interestingly (and simply) tiered applications.

This message was sent by Atlassian JIRA

View raw message