[CASSANDRA-9532] Provide access to select statement's real column definitions

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.16, 2.1.7, 2.2.0 rc2, 3.0 alpha 1
• Component/s: Legacy/CQL
• Assignee: Sam Tunnicliffe Assign to me
• Reporter: Michael Semb Wever

Authors

Sam Tunnicliffe

Reviewers

Benjamin Lerer

• Created: 02/Jun/15 15:54
• Updated: 04/Oct/19 16:20
• Resolved: 18/Jun/15 16:57

Description

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.