cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9664) Allow MV's select statements to be more complex
Date Thu, 03 Sep 2015 18:25:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729513#comment-14729513
] 

Tyler Hobbs commented on CASSANDRA-9664:
----------------------------------------

Okay, I've pushed [a commit|https://github.com/thobbs/cassandra/commit/560450db2cfa74b12ef39d80eeb2ffc77eebe37b]
that switches to using a single string for the where clause in the schema.  This actually
turned out to be fairly simple, and reduces some of the complexities in the patch.

I also pushed a second commit to stop using apache common's StringUtils, which was causing
problems with the dtests.

> 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)

Mime
View raw message