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

Robert Jackson commented on CASSANDRA-2500:
-------------------------------------------

As is now (even if this were pulled into trunk for 0.8.1) to have CQL support 
in any meaningful way we would need to follow the exact same steps as with the 
thrift interface.  I'm not sure how that would be better.

I'm not sure, but it seems to me that the desired result of keeping the CQL 
drivers in-tree would be to make sure that they are functional at release time. 
 If that is correct, but the only way to use the in-tree driver is by 
"vendoring" the code into a third party library what is the point? The end 
user/developer would be in a very similar situation as with the thrift 
interface. (Just copying in these ruby files instead of generating new ones via 
"thrift --gen rb".)

If we want the driver to be in-tree (which I definitely understand) then it 
would seem to make sense to push out an updated gem when the API changes with 
each release.  Similar to how an updated pom is pushed to Maven for the java 
cql driver.  If that were the case then to have a fully functional CQL api we 
would simply have to require a cassandra_cql gem (or something).  Then we could 
build support into our project/gem that would be able to take advantage of the 
fact that this is kept in tree.

I apologize if all of this has already been hashed out, and I definitely 
appreciate your position of wanting to have some degree of control over the 
client library interface.  I also clearly see CQL as an AWESOME step forward. 
It will certainly be the main mechanism for communicating with Cassandra once 
the API is fully implemented.

> Ruby dbi client (for CQL) that conforms to AR:ConnectionAdapter
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-2500
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2500
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Jon Hermes
>            Assignee: Jon Hermes
>         Attachments: 2500.txt, genthriftrb.txt
>
>
> Create a ruby driver for CQL.
> Lacking something standard (such as py-dbapi), going with something common 
> instead -- RoR ActiveRecord Connection Adapter 
> (http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/AbstractAdapter.html).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to