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 Thu, 17 Sep 2015 16:10:04 GMT


Sylvain Lebresne commented on CASSANDRA-9664:

bq. What do you think about leaving getRawText()/getText() and using that for toString() where
it makes sense?

I though about it and figure that it would be perfect if {{Term.Raw}} was an abstract class
(cause if we re-declare {{toString()}} every time, it's better than nothing but a bit ugly
imo) but that we probably wouldn't want to make it an abstract class. That said, I just remembered
that interface now have default functions, so if we can use that, that works for me.

> 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