cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7396) Allow selecting Map key, List index
Date Wed, 24 May 2017 08:15:04 GMT


Benjamin Lerer commented on CASSANDRA-7396:

bq. {{WRITETIME()}} + {{TTL()}} don’t work with element/slice selections, but UDFs + CAST
do work with element/slice selections.

This will require some significant refactoring to the {{Selector}} classes as well as to the
{{Selection}} and {{ResultSetBuilder}} classes. Due to that I think it is best to do that
improvement within CASSANDRA-8877.

I have pushed a new version of the patch [here|]
to fix the remaining issues. I ran the tests on our internal CI and the results look good.

I renamed {{isTerminal}} to {{areAllFetchedColumnsKnown}} as the original name was misleading.
If we have a query like: {{SELECT m\['1'\] + ? FROM myTable}} we do not need to have all the
parameters bound to build the {{ColumnFilter}}. 

> Allow selecting Map key, List index
> -----------------------------------
>                 Key: CASSANDRA-7396
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: CQL
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>              Labels: cql, docs-impacting
>             Fix For: 4.x
>         Attachments: 7396_unit_tests.txt
> Allow "SELECT map['key]" and "SELECT list[index]."  (Selecting a UDT subfield is already

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message