cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9532) Provide access to select statement's real column definitions
Date Fri, 05 Jun 2015 09:45:02 GMT


Sam Tunnicliffe updated CASSANDRA-9532:
    Attachment: 9532-2.0-v2.txt

[~michaelsembwever] I've attached interim patches for 2.0 -> trunk which make the mappings
between the actual columns used in a selection and those in the resultset metadata. It's not
a complete solution yet but if you get a chance, have a look and let me know if this sort
of thing would work for you.

> Provide access to select statement's real column definitions
> ------------------------------------------------------------
>                 Key: CASSANDRA-9532
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: mck
>            Assignee: mck
>             Fix For: 3.x, 2.1.x, 2.0.x, 2.2.x
>         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
> 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

This message was sent by Atlassian JIRA

View raw message