[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087730#comment-13087730
]
T Jake Luciani commented on CASSANDRA-2474:
-------------------------------------------
Understood, thx.
The core issue is we can't work around using special keywords like column and
key in the hive predicates without altering the hive metastore.
What I think we can do to get us closer is create some UDFs to replace the
Keywords so you could do:
{code}
SELECT transposed() FROM foo WHERE key()=X AND column() > X and column() < Y;
{code}
These UDFs would hook into the cassandra hive driver and return the correct row
or column depending on the cursor.
I think we need to do a POC to verify if this is truly possible but I believe
it just might work.
For CQL we could obviously not require the () and use actual keywords.
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: Sub-task
> Components: API, Core
> Reporter: Eric Evans
> Labels: cql
> Fix For: 1.0
>
>
> For the most part, this boils down to supporting the specification of
> compound column names (the CQL syntax is colon-delimted terms), and then
> teaching the decoders (drivers) to create structures from the results.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
