[jira] [Updated] (CASSANDRA-9532) Provide access to select statement's real column definitions

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Tunnicliffe updated CASSANDRA-9532:
---------------------------------------
    Component/s: CQL

> 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
>          Components: CQL
>            Reporter: mck
>            Assignee: Sam Tunnicliffe
>             Fix For: 2.0.16, 2.1.7, 2.2.0 rc2, 3.0 alpha 1
>
>         Attachments: 9532-2.0-v2.txt, 9532-2.1-v2.txt, 9532-2.2-v2.txt, 9532-trunk-v2.txt, cassandra-2.0-9532.txt, cassandra-2.1-9532.txt, cassandra-2.2-9532.txt, trunk-9532.txt
>
>
> 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)