Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 2 Jun 2015 15:55:17 +0000 (UTC)
From: "mck (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12834645.1433260482000.94919.1433260517332@Atlassian.JIRA>
In-Reply-To: <JIRA.12834645.1433260482000@Atlassian.JIRA>
References: <JIRA.12834645.1433260482000@Atlassian.JIRA>
 <JIRA.12834645.1433260482409@arcas>
Subject: [jira] [Created] (CASSANDRA-9532) Provide access to select
 statement's real column definitions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

mck created CASSANDRA-9532:
------------------------------

             Summary: 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)