[
https://issues.apache.org/jira/browse/CASSANDRA-9664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876399#comment-14876399
]
Tyler Hobbs commented on CASSANDRA-9664:
----------------------------------------
bq. I now get an NPE when not providing a where clause
Fixed and added a test for this, thanks.
bq. that this is broken if the identifier has a quote itself as we need to
escape it. And I think it's high time we add a ColumnIdentifier.toCQLString()
that does the right thing
Thanks for pointing that out. I've created {{ColumnIdentifier.toCQLString()}}
as you suggested, and updated a test to cover this.
I've also merged the latest 3.0/trunk into my branches to get clearer test
results and resolve a few merge conflicts.
> Allow MV's select statements to be more complex
> -----------------------------------------------
>
> Key: CASSANDRA-9664
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9664
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Carl Yeksigian
> Assignee: Tyler Hobbs
> Labels: client-impacting, doc-impacting
> Fix For: 3.0.0 rc1
>
>
> [Materialized Views|https://issues.apache.org/jira/browse/CASSANDRA-6477] add
> support for a syntax which includes a {{SELECT}} statement, but only allows
> selection of direct columns, and does not allow any filtering to take place.
> We should add support to the MV {{SELECT}} statement to bring better parity
> with the normal CQL {{SELECT}} statement, specifically simple functions in
> the selected columns, as well as specifying a {{WHERE}} clause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
