[
https://issues.apache.org/jira/browse/CASSANDRA-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064216#comment-13064216
]
Rick Shaw commented on CASSANDRA-2888:
--------------------------------------
Right now (1.0.4-SNAPSHOT) we just return NULL for this call. Please be
specific as to what you think is REQUIRED to work with your toolset (What is it
BTW?) and we can look into providing a simplistic sparse implementation of
static items. I believe the dynamic stuff is way beyond the scope of what can
be done in the midst of the other items in the roadmap for 1.1. We can tackle
the dynamic stuff when CQL decides how it will format the data in a structured
({{CQLResult}}) response.
> CQL support for JDBC DatabaseMetaData
> -------------------------------------
>
> Key: CASSANDRA-2888
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2888
> Project: Cassandra
> Issue Type: Improvement
> Components: Drivers
> Affects Versions: 0.8.1
> Environment: J2SE 1.6.0_22 x64 on Fedora 15
> Reporter: Dave Carlson
> Assignee: Rick Shaw
> Priority: Minor
> Labels: cql, newbie
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> In order to increase the drop-in capability of CQL to existing JDBC app
> bases, CQL must be updated to include at least semi-valid responses to the
> JDBC metadata portion.
> without enhancement:
> >>> com.largecompany.JDBCManager.getConnection("<vague Cassandra JNDI
> >>> pointer>")
> Resource has error: java.lang.UnsupportedOperationException: method not
> supported
> ...
> with enhancement:
> >>> com.largecompany.JDBCManager.getConnection("<vague Cassandra JNDI
> >>> pointer>")
> org.apache.cassandra.cql.jdbc.CassandraConnection@1915470e
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
