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

Sylvain Lebresne commented on CASSANDRA-11602:
----------------------------------------------

bq. Any response?

We appreciate your input, but as we said, we have currently no way to implement 
this in a non _very_ inefficient way, and our experience is that something that 
inefficient deserves C* more that it helps because no-one will end up using it 
due to the awful performance but people will get burnt by it first.

If you disagree or have some idea on how to make this efficient, you are 
welcome to provide a patch as well as sufficient benchmark evidence that it 
performs acceptably.

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

Reply via email to