[
https://issues.apache.org/jira/browse/CASSANDRA-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-4964.
---------------------------------------
Resolution: Invalid
Sorry, this reflects a fundamental misunderstanding of how cql3 maps to the
storage engine. Please see
http://www.datastax.com/dev/blog/cql3-for-cassandra-experts and
http://www.datastax.com/dev/blog/thrift-to-cql3.
> Return column metadata for dynamic columns
> ------------------------------------------
>
> Key: CASSANDRA-4964
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4964
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.6
> Reporter: Peter Lin
>
> Currently, org.apache.cassandra.thrift.CqlMetadata doesn't return the column
> name and value metadata for dynamic columns. If I execute a query against a
> dynamic column that was inserted through thrift or hector, the name and/or
> value type may not be the same as the default types declared in the column
> family definition.
> If the dynamic column was inserted through CQL, it will conform to the
> defined default types for column name and value. Even in that case, it is
> still nice to have the metadata returned. That will facilitate developing
> tools for CQL and make it easier on people writing drivers for Cassandra.
> I'm willing to contribute to this, if someone points me to the right place.
> I've read a lot of the core cassandra code, but I haven't gone through all of
> CQL yet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
