Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 12 Mar 2014 16:35:47 +0000 (UTC)
From: "Russell Bradberry (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12701009.1394641510577.52146.1394642147318@arcas>
In-Reply-To: <JIRA.12701009.1394641510577@arcas>
References: <JIRA.12701009.1394641510577@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6846) Provide standard interface
 for deep application server integration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Russell Bradberry edited comment on CASSANDRA-6846 at 3/12/14 4:34 PM:
-----------------------------------------------------------------------

+1 I'd like to take it one step further and even make parts of Cassandra, like CQL, use the interface as well.  Something of eating one's own dog food.  That way the interface will grow with the features that are added to things like CQL and it won't be a constant battle of "Feature X was added to CQL can we please get it exposed in the interface"


was (Author: devdazed):
:+1: I'd like to take it one step further and even make parts of Cassandra, like CQL, use the interface as well.  Something of eating one's own dog food.  That way the interface will grow with the features that are added to things like CQL and it won't be a constant battle of "Feature X was added to CQL can we please get it exposed in the interface"

> Provide standard interface for deep application server integration
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-6846
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6846
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Tupshin Harper
>            Assignee: Tupshin Harper
>             Fix For: 3.0
>
>
> 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
(v6.2#6252)