cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9664) Allow MV's select statements to be more complex
Date Fri, 18 Sep 2015 07:48:05 GMT


Sylvain Lebresne commented on CASSANDRA-9664:

bq.  I now get an NPE when not providing a where clause

Definitively something to fix.

bq. quotes all column names, even if they are all in lowercase

It was done out of simplicity (quoting unconditionally in the code), but that made realize
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 (and
could easily avoid quoting when not required so it's a bit nicer), especially since CASSANDRA-10217
also has to do this and there is no point in not having that in only one place. 

> Allow MV's select statements to be more complex
> -----------------------------------------------
>                 Key: CASSANDRA-9664
>                 URL:
>             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|] 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

View raw message