cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Yeksigian (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11602) Materialized View Doest Not Have Static Columns
Date Thu, 28 Apr 2016 15:57:12 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carl Yeksigian updated CASSANDRA-11602:
---------------------------------------
    Fix Version/s: 3.x
                   3.0.x
           Status: Patch Available  (was: Open)

I agree with [~slebresne] that the performance of static columns in MV would be surprising
to users, specifically needing to read an entire partition; even if we do decide to add support,
we would want to wait until after CASSANDRA-11475 is committed.

Previously, it looks like we warned if the static column was explicitly selected, and silently
dropped if it was included in a {{SELECT *}} for the view. I changed that to throw an exception
if a static column is explicitly selected, and to warn if it is dropped when using a {{SELECT
*}}.

|| 3.0 || trunk ||
| [branch|https://github.com/carlyeks/cassandra/tree/ticket/11602/3.0] |  [branch|https://github.com/carlyeks/cassandra/tree/ticket/11602/trunk]
|
| [utest|http://cassci.datastax.com/view/Dev/view/carlyeks/job/carlyeks-ticket-11602-3.0-testall/]
| [utest|http://cassci.datastax.com/view/Dev/view/carlyeks/job/carlyeks-ticket-11602-trunk-testall/]
|
| [dtest|http://cassci.datastax.com/view/Dev/view/carlyeks/job/carlyeks-ticket-11602-3.0-dtest/]
| [dtest|http://cassci.datastax.com/view/Dev/view/carlyeks/job/carlyeks-ticket-11602-trunk-dtest/]
|

> Materialized View Doest Not Have Static Columns
> -----------------------------------------------
>
>                 Key: CASSANDRA-11602
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11602
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Ravishankar Rajendran
>            Assignee: Carl Yeksigian
>             Fix For: 3.0.x, 3.x
>
>
> {quote}
> CREATE TABLE "team" (teamname text, manager text, location text static, PRIMARY KEY ((teamname),
manager));
> INSERT INTO team (teamname, manager, location) VALUES ('Red Bull1', 'Ricciardo11', 'Australian');
> INSERT INTO team (teamname, manager, location) VALUES ('Red Bull2', 'Ricciardo12', 'Australian');
> INSERT INTO team (teamname, manager, location) VALUES ('Red Bull2', 'Ricciardo13', 'Australian');
> select * From team;
> CREATE MATERIALIZED VIEW IF NOT EXISTS "teamMV" AS SELECT "teamname", "manager", "location"
FROM "team" WHERE "teamname" IS NOT NULL AND "manager" is NOT NULL AND "location" is NOT NULL
PRIMARY KEY("manager", "teamname");  
> select * from "teamMV";
> {quote}
> The teamMV does not have "location" column. Static columns are not getting created in
MV.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message