cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9532) Provide access to select statement's real column definitions
Date Tue, 02 Jun 2015 16:49:49 GMT

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

mck commented on CASSANDRA-9532:
--------------------------------

jira went down like that minute :-)

> Provide access to select statement's real column definitions
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-9532
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9532
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: mck
>            Assignee: mck
>
> Currently there is no way to get access to the real ColumnDefinitions being used in a
SelectStatement.
> This information is there in
> {{selectStatement.selection.columns}} but is private.
> Giving public access would make it possible for third-party implementations of a {{QueryHandler}}
to work accurately with the real columns being queried and not have to work-around column
aliases (or when the rawSelectors don't map directly to ColumnDefinitions, eg in Selection.fromSelectors(..),
like functions), which is what one has to do today with going through ResultSet.metadata.names.
> This issue provides a very minimal patch to provide access to the already final and immutable
fields.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message